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.

Getting Started

Getting Started

Learn about our Authentication Framework

The Authentication Framework protects access to user data via modern, battle-tested, tech industry standards such as OAuth 2.0 and OpenID Connect (OIDC) (which we continue to update as those standards evolve).

See Authentication Framework for details.

Authentication framework purpose

The Authentication Framework is the underlying foundation for consuming all Jack Henry Enterprise APIs (e.g. the Wires API and EDPP AP).

The Authentication Framework does not use API keys nor does it share usernames and passwords with 3rd party developers.

Instead, it provides authorized API access via an Access Token and provides authenticated information about the user via an Identity Token.

OAuth 2.0 and OpenID Connect

The Authentication Framework protects user data using the OAuth 2.0 industry standard. With OAuth, users can delegate scoped access to third parties who wish to act on the user’s behalf. The user’s login credentials are never shared with the third party. Instead, authorization is provided to third party apps via an access token.

The Authentication Framework provides user identity information using the OpenID Connect (OIDC) industry standard. OpenID Connect is an identity layer built on top of the OAuth 2.0 protocol. With OpenID Connect, third party apps are provided authenticated information about the user in the form of an identity token.

Tokens

OAuth 2.0 and OpenID Connect are based on the concept of tokens. There are 3 main types:

  • Access Token
  • Identity Token
  • Refresh Token

External resources for OAuth 2.0 and OpenID Connect

If you want to learn more about OAuth 2.0 and OpenID Connect, these external resources may be useful:

API credentials

Obtaining

Testing/development credentials are only available to JH partner banks and VIP participating vendors.

  • If you are a partner bank, please submit For Clients Case and ask it to be routed to EIS Adoption.
  • For VIP participants, submit a Vendor/Partner Portal case.

Usage

Client Authentication:

  • client_id
  • client_secret
Keep it secret
It is important to keep the client_id and client_secret values secret and not leak it through some kind of frontend, client-accessible JavaScript call.
Don't share or commit it

Do not share credentials via unsecured channels (e.g. email or instant messaging)

Similarly, do not commit credentials to your source code repository.

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 Thu Mar 6 2025