Developer Programs

Learn

Docs

Connectivity Options for JH Hosted API Services

Getting Started > Connectivity Options for JH Hosted API Services

Overview

This page outlines the only supported connectivity methods for third party applications to access services hosted in Jack Henry Data Centers, utilizing jXchange and SymXchange integration services.

We are committed to maintaining the highest standards of security, compliance, and operational integrity. As such, access is strictly limited to these methods.

Connectivity Grid

The following table details the current and future approved connectivity options for jXchange and SymXchange. All other connection methods are unsupported and prohibited.

API ServicePublic InternetVPN/IP SecLegacy Security ProtocolNew Security ProtocolImportant Notes
jXchangeYesYesUsername/PasswordOAuth 2.0Username/Password Sunset Date: This method will be deprecated on April 30, 2028. Migration to OAuth 2.0 is highly recommended. See our documentation.
SymXchangeYes*YesUsername/PasswordmTLS or VPN/IPSecUsername/Password. SymXchange connections will require either mTLS or VPN/IPSec connectivity by Nov 1, 2028.
Other/ODI/FTPN/AYesN/AN/AAll file based traffic must use VPN/IPSec protocols.
SymXchange Note
This is only available for EASE and will be deprecated and replaced by IPSec/mTLS.

In addition to jXchange, all other Jack Henry Gateways utilize OAuth 2.0 public internet


Hosted Hardware in Our Data Centers

This is a security and compliance measure. Allowing external, unmanaged hardware introduces unacceptable risks, including:

  • Security Vulnerabilities: External hardware could create new attack vectors (backdoors, unauthorized network access) that are outside of our direct security and auditing control.
  • Operational Risk: External hardware could introduce stability and reliability issues, such as conflicts, power consumption spikes, or cooling demands, potentially impacting the uptime and performance of other services.
  • Complex Auditing: Vetting and continuously monitoring the security posture of every piece of third-party equipment would create a prohibitive and complex auditing burden.
  • Operational Overhead: Space consumption.

By limiting access to strictly-defined, controlled network and authentication methods, we can ensure a secure, resilient, and compliant environment for all integrators and customers.


Have a Question?
Have a how-to question? Seeing a weird error? Get help on StackOverflow.
Register for the Developer Office Hours where we answer technical Q&A from the audience.

Did this page help you?

Last updated Wed Nov 5 2025