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

Health Check

Tutorials > Health Check

I would like to perform a health check to verify that jXchange is operational.

Ping API Overview

You may notice the Ping API in the XSD/WSDL and consider implementing it. However, the Ping API is a legacy API that relies on a default configuration applied within jXchange.

Limitations:

  • Ping only confirms that the jXchange instance is online.
  • It does not provide status information for service providers or cores.
  • It does not indicate whether a specific provider (e.g., Silverlake) is available for a given FI.

Similar health‑check behavior can be achieved using Search or Inquiry‑type APIs, which do not rely on default configurations and provide more meaningful results.

For example:

  • To verify that Silverlake is online for a specific FI, a vendor can invoke a search‑type API such as CustSrch.
  • A successful response confirms that both jXchange and the underlying core provider are responding for that FI.

This approach offers a more reliable validation of end‑to‑end availability than the Ping API.

Have a Question?
Did this page help you?
Last updated Fri Feb 6 2026