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

Accounts API

Manage your accounts programmatically. Create new accounts, retrieve details and balances, and organize all your client accounts in one place. This allows you to automate account operations and keep your financial data up to date with ease.

Accounts 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 Account Restrictions and Account. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 3 paths, and defines 30 schemas. It is described by OpenAPI 3.2.0, at version 2.0.55.

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

5 operations 3 paths 30 schemas 3 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.55
Base URL
https://api.payments.jpmorgan.com/embedded/v2
Contact
JPMC Technical Services Support
Resource Areas
1

Paths & Operations 5

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

Accounts 5

Create, organize and manage accounts.

GET
/accounts
List accounts
getAccountsListV2 3 params → 200400401403404500503
POST
/accounts
Create account
postAccountsV2 2 params body → 202400401403404500503
GET
/accounts/{id}
Get account
getAccountsV2 3 params → 200400401403404500503
PATCH
/accounts/{id}
Manage account
manageAccountsV2 3 params body → 202400401403404500503
GET
/accounts/{id}/balances
Get an account balance
getAccountBalance 3 params → 200400401403404500503

Schemas 30

The contract defines 30 schemas that model the data the API accepts and returns. The most detailed are GetAccountResponseV2 (12 properties), CreateAccountResponseV2 (8 properties), CreateAccountRequestV2 (7 properties), AccountRestrictionV2 (5 properties). Each schema is shown below with its type and property counts.

ClientIdV2
string
The id of the approved client created via the /clients endpoint
CreateAccountResponseV2
object
8 properties 2 required
GetAccountResponseV2
object
12 properties 5 required
ClientRequestedClosureReason
string
Reason for account closure. This field is included when an account closure has been requested. Valid values include: | Value | Description | |-------|---------…
LabelV2
string
The label of the account to be created. Currently, only MAIN is supported and used only when the category is LIMITEDDDA or LIMITEDDDAPAYMENTS
ApiErrorReasonV2
object
Schema representing detailed reasons for an API error, including code, location, and message.
4 properties 1 required
AccountBalanceV2
object
3 properties 3 required
BalanceLimitsV2
object
Balance limits the account is allowed to have
2 properties
AccountParentIdV2
string
The id of the parent SUMMARYACCOUNT when creating a TRANSACTIONACCOUNT or SUMMARYACCOUNT
ManageAccountResponseV2
object
5 properties 1 required
StateV2
string
State of the account. Valid values are: | Value | Description | |-------|-------------| | OPEN | Account is open and operational | | PENDINGOPEN | Account open…
AccountBalanceDtoV2
object
2 properties 2 required
PaymentRoutingInformationRequestV2
object
Payment routing information request
1 property 1 required
CreateAccountRequestV2
object
7 properties 1 required
LabelResponseV2
string
Account label
UpdatedAtV2
string
Date and time the account was last updated
RoutingInformationV2
object
Routing information
3 properties 2 required
GetAccountsListResponseV2
object
2 properties 2 required
ManageAccountRequestV2
object
4 properties
AccountIdV2
string
The resource Id of your account to use when looking up details of this account or making payments
PageMetaData
object
3 properties
AccountCategoryRequestV2
string
Depending on your pathway, the category of the account can be one of the following: | Value | Description | |-------|-------------| | SUMMARYACCOUNT | Summary…
PaymentRoutingInformationV2
object
Payment routing information
4 properties 3 required
AccountCategoryResponseV2
string
Category of the account. Valid values are: | Value | Description | |-------|-------------| | SUMMARYACCOUNT | Summary account | | TRANSACTIONACCOUNT | Transact…
ApiErrorV2
object
Schema representing a version 2 API error, including title, HTTP status, and additional context.
5 properties 1 required
ClosureReasonV2
string
Reason for account closure
CreatedAtV2
string
Date and time the account was created
AccountRestrictionV2
object
List of restriction properties
5 properties 5 required
RestrictionsV2
array
List of restrictions applied to the account
AccountBalanceResponseV2
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs JPMorgan Chase publishes across the network.

Notifications 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
JPMorgan Chase Account Validation API
Where this information came from

This is an independent, third-party profile of Accounts 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.