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.

Overview

Consumer API > Overview

The Consumer API uses modern technologies to provide a rich, consistent developer experience.

Likewise, it adopts modern standards to secure access to user’s financial data.

Authentication

The Consumer API uses the Authentication Framework to provide secure authentication.

See the Authentication Framework docs for details that apply to all authentication schemes.

See the Authentication topic for authentication details specific to the Consumer API.

REST and JSON

The Consumer API is based on REST and has predictable resource-oriented URLs.

The Consumer API uses standard HTTP verbs and status codes and returns JSON-encoded responses.

The Application Ecosystem

The Banno Digital Platform™ is a multi-tenant service, which means many different financial institutions exist on the platform. Because of this, there are a few other things to keep in mind when developing an application using the Consumer API:

External Applications

  1. Each financial institution can enable many different external applications
  2. Each external application can have multiple Redirect URIs

Plugin Configurations

  1. Each plugin is powered by at least one external application
  2. Each financial institution can enable many different plugins

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
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 Tue Jul 11 2023