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 Consumer API protects access to user data using OAuth 2.0. The user’s login credentials are never shared with third party apps. Authorization is provided to third party applications via an access_token.
The Consumer API provides authenticated user identity information using OpenID Connect (OIDC). With OpenID Connect, third party apps are provided authenticated information about the user in the form of an identity_token.
Both the access_token and identity_token are encrypted in JSON Web Token format.
See the Base URL topic.
See the Versioning topic.
Date and Time
See Date and Time.
API endpoints are protected by an OAuth / OpenID Connect scope as part of the Permissions Flow.
The OAuth / OpenID Connect scope required for a specific API endpoint can be found in the endpoint’s definition in the API Reference.
See the Authentication topic for more details.
Before you get started, you’ll need to get these from the back office administrator at your financial institution who has access to Banno People.
If the administrator does not know where to do this, they can review the External application configuration article on the Banno Knowledge site.
You’ll need these credentials:
- client_secret <— Keep this secret!
Similarly, do not commit credentials to your source code repository.