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.

OAuth 2.1

Concepts > Advanced Topics > OAuth 2.1

What is it?

The OAuth 2.1 draft specification is an improvement to OAuth 2.0.

What is its purpose?

The purpose of OAuth 2.1 is to simplify and solidify the best practices from various OAuth 2.0 extensions.

For example, OAuth 2.1 requires PKCE for all OAuth clients which use the Authorization Code Flow. See the PKCE topic for more details.

OAuth 2.1 also eliminates existing OAuth 2.0 features which were problematic, in practice, from a security perspective.

How do I use it?

The Authentication Framework already includes support for OAuth 2.1 in anticipation of the draft specification being approved in the near future.

Have a Question?
Did this page help you?
Last updated Mon Mar 24 2025