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.

GitHub Access

Getting Started > GitHub Access
GitHub
GitHub

You will need access to the Jack Henry enterprise in GitHub. All jhDocs repos are in GitHub.

There are also organizations within the Jack Henry enterprise in GitHub. Check with your team to figure out which organization within Jack Henry GitHub that your documentation site repos belong in.

Request this access from the Jack Henry help desk for yourself and for any team members who will be updating this repo, if you don’t already have it.

Organization secret required in GitHub organizations

jhDocs relies on an GitHub organization secret named JHDOCS_PRIVATE_KEY having been defined in your repo’s GitHub org in order to function. We currently have this secret defined in the jhky, banno, and JHADigitalCore organizations in Jack Henry GitHub.

If you’re using jhDocs in an organization other than jkhy, banno, or JHADigitalCore, contact us and ask us to set up that organization secret.

Learning resources

If you would like to learn more about git and GitHub, here are some online resources that can help you understand how git and GitHub work together.

Next topic: Installing Third-Party Utilities
Support options
Have questions on this topic?
Join the jhDocs team in Microsoft Teams to connect with the community.
See something in this page that needs to change?
Send us feedback on this page.
Did this page help you?
Last updated Fri Dec 19 2025