Developer Programs
Getting Started
Get started working with Jack Henry's developer programs today.
Fintech Integration Network (FIN)
Jack Henry's Integration Program for Fintechs.
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.
Digital Core
Modernize with cloud-native core banking technology.
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.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.
jXchange REST-Legacy Migration announced. Deadline for migration is July 31, 2026.
More info

jXchange Environment

Overview > Portal Navigation > jXchange Environment

The jXchange Environment section of our portal serves as a centralized resource for all key information related to the jXchange environment. Below is a summary of each subpage to help you quickly locate relevant details.

jXchangeHdr Information

jXchange APIs use the jXchangeHdr portion of the XML request to manage routing, API usage, and security. The jXchangeHdr Information page explains each element within this XML structure.

Multi-Endpoint Support

The jXchange environment supports both single-tenant and multi-tenant applications with multiple endpoints. The Multi-Endpoint Support page includes high-level diagrams illustrating how this is implemented.

jXchange Connector

The jXchange Connector pages discuss the production-ready MuleSoft integration that simplifies development and usage of the jXchange/Service Gateway APIs. Key resources include:

  • Release Notes
  • User Manual
  • Technical Reference Document

jXchange and (Core Director, CIF/2020 and SilverLake)

The three primary banking cores in the jXchange-SOAP API environment — CIF 20/20, Core Director, and SilverLake — have differences in how they handle and expose data. These pages help developers working across multiple cores understand those differences:

jXchange Behaviors

The jXchange Behaviors page covers various environmental behaviors when working with jXchange SOAP APIs. Topics include:

  • Use of “X” elements to limit inquiry responses
  • Message Transmission Optimization Mechanism (MTOM)
  • Routing across institutions and environments
  • Cursor-based search request/response behavior
  • Wildcard search usage
  • End-of-day core processing behavior

jXchange Service Gateway Manual

The jXchange Service Gateway Manual provides a high-level overview of the jXchange/Service Gateway environment, including:

  • Technical recommendations
  • Release cycle details
  • Compatibility and transparency
  • Best practices
  • Development environment setup
  • Security guidelines

jXchange Error Handling

The jXchange Error Handling page explains how to interpret and respond to provider-level error messages. For integration or communication errors, refer to the Error Types page.

Have a Question?
Did this page help you?
Last updated Mon Feb 2 2026