Developer Programs
Vendor Integration Program (VIP)
Direct access to Jack Henry's technical integration resources.
Technical Account Manager (TAM)
Get technical integration help from a single point of contact.
Developer Account
Create a developer acccount to access resources that help you integrate with Jack Henry.
Learn
Shared Responsibility
Learn about shared roles and responsibilities of customers and Jack Henry in open banking.
Developer Use Cases
Find a use case that fits your development needs.
Developer Video Gallery
Watch the latest demos, webinars, and more.
Developer Conference
Connect with industry leaders, gain insights from expert speakers, and explore our latest innovations.
Docs
Admin API
Create solutions for an institution's back office support tools.
Authentication Framework
Map customer identities to your existing system IDs.
Consumer API
Access financial data for user accounts, transactions, and more.
Data Hub
Get deeper access to financial institution data.
Enterprise Event System
Respond to events in real-time using this powerful pub/sub-based solution.
jXchange - REST API
Translate business information between Jack Henry and 3rd-party apps using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and 3rd-party apps using a SOAP-based API.
Operational Data Integration (ODI)
Get customized queries for bulk data needs.
Payments
Embed check deposits, ACH, bill pay, cards, and real-time payments.
Plugin Framework
Embed the best of the fintech world directly into your user's dashboard.
SymXchange
Query Symitar core member accounts, post transactions, run PowerOn scripts, and more.
Xperience
Modern UI that provides consistent visual integration across Jack Henry products.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.

JH Wires

Pipelined Data Sets > JH Wires

Introduction

The goal of this pipeline is to make the JH Wires dataset available in Google Big Query where it can be queried using the SQL interface for business purposes and to drive downstream business processes.

Pipelines

The JH Wires pipeline is made of of two different components.

The Wire-Search-Service receives history data for incoming and outgoing wires via the ‘WireDataUpdated’ event from the Incoming and Outgoing Wire Services. The history data includes details such as WireId, UniversalInstitutionId, CreationDate, ApplicationId, CssCorrelationId, InstitutionId, and other wire-specific state data with both old and new values, such as process step, state, and change user. This data is pushed to Data Hub on each raised ‘WireDataUpdated’ event. This data is written to big query in Data Hub via Rest API service and not Kafka PUSH. The configuration details include setting up ProjectId, DataSetId, and TableId in AppSettings on wires that match the configuration on the Data Hub project. The appropriate read-write permissions were granted to the service account configured for Wire-Search-Service that communicates with Data Hub.

The JH Wires ISO pipeline utilizes BigQuery External Connections in the Data Hub project, to the Publisher Spanner database in their project. Federated Queries are used with these External Connections to pull data from the Spanner Database into the BigQuery dataset / tables.

Topics in this section

Have a Question?
Have a how-to question? Seeing a weird error? Get help on StackOverflow.
Register for the Digital Toolkit Meetup where we answer technical Q&A from the audience.
Last updated Tue Mar 4 2025