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.

Troubleshooting

Troubleshooting
GitHub
GitHub
If you are having issues with jhDocs, try troubleshooting the issues by stepping through the info below.

When my site is deployed, I can see the content, but everything looks awful

The baseURL setting in your config.yaml file must include the fully qualified URL to your site, including a slash on the end.

If you don’t have this set up properly, your site won’t be able to access the CSS and JavaScript resources needed for the site to render or behave as expected.

This can be an easy step to forget if you’re temporarily deploying your site to a different location than normal, say for testing purposes. If you leave the baseURL setting at its typical value, it won’t be readable from the new location.

Why does my site have a strange URL in GitHub Pages?

You have to mark the GitHub Pages visibility setting to a value of “Public” in settings (Settings > Pages > GitHub Pages > GitHub Pages visibility) in order to get a site URL that matches your repo name.

Private sites in GitHub Pages get a generated name that has nothing to do with your repo name, which is typically not what you want.

Next topic: Support
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 Mon Dec 29 2025