How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

JPMorgan Chase Consents API

Account Information - Consents

JPMorgan Chase Consents API is one of 65 APIs that JPMorgan Chase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Consents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 3 paths, and defines 53 schemas. It is described by OpenAPI 3.2.0, at version 2.0.22.

Requests are made against 3 base URLs: https://api.payments.jpmorgan.com/paybybank/v2, https://api-cat.payments.jpmorgan.com/paybybank/v2, https://api-mock.payments.jpmorgan.com/paybybank/v2.

4 operations 3 paths 53 schemas 1 DELETE1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.22
Base URL
https://api.payments.jpmorgan.com/onboarding/v1
Resource Areas
1

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 1 DELETE, 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Consents 4

Account Information - Consents

POST
/consents
Initiate Consent Journey
initiateConsent 3 params body → 201400401403429503
GET
/consents/{consentId}
Get consent status
getConsentStatus 3 params → 200400401403404422429503
DELETE
/consents/{consentId}
Revoke consent
revokeConsent 4 params → 204400401403404422429503
POST
/consents/{consentId}/renew
Renew consent
renewConsent 4 params body → 200400401403404422429503

Schemas 53

The contract defines 53 schemas that model the data the API accepts and returns. The most detailed are ConsentBasic (13 properties), ConsentLinkRequest (8 properties), Address (7 properties), WebHook (7 properties). Each schema is shown below with its type and property counts.

AdditionalContext
object
3 properties 3 required
PartyRole
string
The role of the party to the account.
Error
object
Error details for consent processing issues
3 properties 2 required
Phone
object
Representation of a Phone Number
2 properties
FinancialInstitutionIdType
string
Financial Institution Identifier Type
AccountDetail
object
Consented accounts details
4 properties 1 required
WebHook
object
Webhook Data
7 properties 6 required
ConsentRenew
object
Consent renew or re-consent request for continuous access to existing consented information
2 properties
UpdateConsentLinkResponse
object
Representation of the details necessary to start and track the consent journey.
ConsentLinkWithView
object
Representation of a generated consent link.
PartyIdentity
object
Representation of a party with its role, identity, and verification status.
4 properties
IdempotencyKey
string
A string that enables the API support idempotency by safely retrying requests without accidentally performing the same operation twice.
AccountBasic
object
Basic representation of a financial account.
7 properties
ApiErrorContext
object
The API error context object returned by the API.
5 properties 1 required
Value
object
Value
2 properties 2 required
ConsentLinkType
string
Type of consent link that defines how account connects. | Consent Link Type | Description | |:------------------|:---------------------------------------------…
ConsentLinkRequest
object
Representation of a User's consent detail for accessing financial data
8 properties 3 required
AccountStatus
string
Account Status
ConsentLink
object
Representation of a generated consent link.
3 properties 2 required
ConsentLinkInitiated
object
Consent Link event published as part of account linking flow for consent link URL is generated
2 properties 2 required
ConsentStatus
string
Type of consent status | Consent Status | Description | |:---------------------|:--------------------------------------------------------------------------| |…
ConsentLinkId
string
Unique identifier to access Pay by Bank UI for Link (UUID)
ConsumerProfileId
string
Internal consumer profile identifier provided by JPMC
ApiAdditionalContext
object
3 properties 3 required
FinancialInstitution
object
Represents a financial institution with its name and logo.
2 properties 1 required
ISOCountryCode
string
ISO 3166-1 Alpha-2 Country Code
RequestId
string
Client provided unique identifier for the current request invocation
ErrorContext
object
4 properties 1 required
ConsentId
string
Unique identifier to access consent resources (UUID)
Amount
string
The value representation of a monetary amount. The amount value should be more than 0.01 with maximum of two decimal places allowed.
ReferenceId
string
A unique identifier provided by the client for the request, which will be returned upon the completion of the consent process.
ConsentBasic
object
Representation of a User's consent details without account information.
13 properties 6 required
ExternalUserProfile
object
Details of the external user.
4 properties
Address
object
Representation of an address object.
7 properties
AccountId
string
Internal account identifier provided by JPMC
ConsentLinkFailed
object
Consent Link event published as part of account linking flow for failure
ConsentDetail
object
Representation of a User's consent detail with account information.
ApiError
object
The error object returned by the API.
5 properties 3 required
TraceId
string
A unique identifier generated by server for tracing the request through the system.
FinancialInstitutionId
object
Financial Institution Identifier
2 properties 2 required
ISOCurrencyCode
string
Currency of the money movement: a 3 alpha character ISO 4217 currency code.
SORTCODE
object
Account identifier specific to the SORTCODE account numbering scheme.
3 properties 1 required
IBAN
object
International bank account number (IBAN) standard numbering system.
4 properties 1 required
Email
object
Representation of detailed email information.
3 properties
ExternalUserId
string
User Id for tracking the external user
ConsentType
string
Type of consent requested, specifying the scope of access to account information | Consent Type | Description | Supported Region | |:-------------------------|…
User
object
Pay by Bank User
1 property
Balance
object
Balance Information
3 properties 2 required
Party
object
Representation of a party with its role, identity, and verification status.
4 properties 1 required
ClientId
string
Unique Identifier of the client that is generated by PBB.
USABA
object
Account Identifier in US Banking account number format
5 properties 1 required
ConsentLinkResponse
object
Representation of the details necessary to start and track the consent journey.
AccountType
string
Specifies the type of account. | Account Type | Description | |----------------|------------------------| | CHECKING | A Checking account. | | SAVINGS | A Savi…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-consents-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Notifications API
Accounts API
Recipients API
Webhooks API
Transactions API
Documents API
JPMorgan Chase Account Information API
JPMorgan Chase Account Restrictions API
JPMorgan Chase Account Services API
JPMorgan Chase Account Statements API
JPMorgan Chase Account Transactions API
JPMorgan Chase Account Updates API
Where this information came from

This is an independent, third-party profile of JPMorgan Chase Consents API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.