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.
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 Broker
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 third-party applications using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and third-party applications 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.

Restrictions

Consumer API > API Reference > Restrictions

The Consumer API is specifically designed to protect the security of the user and protect the user experience.

As such, these are some restrictions to keep in mind as you build your app.

Permissions and scope enforcement

The Consumer API protects access to user data via OAuth / OpenID Connect scopes.

The OAuth / OpenID Connect scope required for a specific Consumer API endpoint can be found in the endpoint’s definition in the API Reference.

See the Authentication topic for more details.

Permissions flow

The Consumer API data permissions are granted based on granular request scopes and claims, which provide limited access to specific data on a per user basis.

See the Permissions Flow topic for more details.

Modifying data on the core platforms

The Consumer API works with data from these core platforms offered by Jack Henry:

Banking Core Platforms

  • SilverLake
  • CIF 20/20
  • Core Director

Credit Union Core Platform

  • Symitar
Modifying core data

Although the Consumer API may modify data on the core as part of its operations, it is not intended to be used as a generic ‘pass through’ for modifying data on the core.

If you need such a solution, we recommend looking into integrating with jXchange (for banks) or SymXchange (for credit unions).

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 Wed Aug 9 2023