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.
Important Notice. JH Datacenter Change announced
More info

JH Datacenter Change

JH Datacenter Change

Overview

This document details the changes that were made for the new JH datacenter connection.

Maintenance Notice: SymXchange Restart & F5 IP Updates

As part of our ongoing infrastructure improvements, we have added new F5 IP addresses to the SymXchange instances supporting your integrations. To ensure these changes take effect and resolve recent connectivity issues, a scheduled SymXchange restart will occur during this weekend’s maintenance window. What’s Changing

  • New F5 IP addresses have been whitelisted for SymXchange instances.
  • The SANDBOX servers are down today for scheduled maintenance.
  • SymXchange will be restarted during maintenance to apply these updates.
  • Affected Fintechs may have experienced 403 errors due to the recent IP changes. This restart is expected to resolve those errors and restore normal connectivity.

Jack Henry™ Changes

  • JH Datacenter domain for SymXchange™ connections is changing from ease-symx.com to ease.jackhenry.com.

  • SymXchange™ communication is now over port 443.

  • A new wild card certificate (*.ease.jackhenry.com) will be used.

  • The new host name will be resolvable in public DNS.

    • If testing does not result in resolution, please wait until 10/31. If the issue persists after that date, email Developer Relations.
    • To test in advance, add a DNS entry in the Fintech environment to resolve the new host name to 52.128.112.49.

  • A unique host name will be used for each SymXchange™ connection to the JH datacenter.

    • CUSTID--<PROD or SANDBOX>-<SYM #>--.ease.jackhenry.com
    • FI Number is an internal JH identifier for the financial institution
    • PROD or SANDBOX refers to Production or Test environment
    • SYM # is the SYM number on the JH Server
    • Instance Name is the name of the Instance
    • Internal JH Port is the Port number used within the JH Network

  • SymXchange™ endpoint address no longer includes a port number.

    • Old: https://:/SymXchange/?wsdl
    • New: https://<hostname/SymXchange/?wsdl

Fintech Consideration

The following must be completed prior to the test:

  • Outgoing traffic to the new endpoint and domain name must be allowlisted through your network.
  • Incoming traffic for receiving responses from the new JH endpoint must be allowlisted.
  • JH must have the IP address for the machine that will be making the connection to the new endpoint.

Testing the Connection

The connection to the new URL should present you with a WSDL page.

  1. Open a new instance of a web browser (any kind).
  2. Copy and paste the domain name into the browser’s URL bar.
  3. Prefix it with https:// and append the very end with /SymXchange. The URL should appear as so:

If the WSDL page appears, (similar to the image below) then the test was successful.

WSDL Page
  1. Confirm with JH to ensure that the correct endpoint was reached.
Did this page help you?
Last updated Mon Dec 29 2025