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

Blockchain Deposit Account Balances API

Access real-time and historical balances for your eligible J.P. Morgan accounts, so you can easily track cash positions and reconcile transactions across up to 100 accounts per request. This API lets you retrieve both current-day and up to 45 days of balance history, helping you streamline your treasury operations and reporting.

Blockchain Deposit Account Balances API is one of 26 APIs that JPMorgan Chase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 2 operations across 2 paths, and defines 20 schemas. It is described by OpenAPI 3.0.0, at version 2.0.7.

Requests are made against 2 base URLs: https://api.payments.jpmorgan.com/account/v2, https://api-mock.payments.jpmorgan.com/account/v2.

2 operations 2 paths 20 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2.0.7
Base URL
https://api.payments.jpmorgan.com/account/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Blockchain Deposit Account Balances API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 2

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

Balances 2

Balance Information

GET
/accounts/balances
Retrieve Balances of All Eligible Accounts
getAccountsBalances 3 params → 200400401403500503
POST
/accounts/balances/inquiry
Inquire Balances
inquireAccountsBalances 3 params body → 200400401403500503

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are Error (5 properties), Account (5 properties), Cursor (5 properties), ErrorContext (4 properties). Each schema is shown below with its type and property counts.

AccountsInquiry
object
Accounts schema used to provide the inquiry criteria based on which account information is retrieved
1 property 1 required
AccountsResponse
object
2 properties 2 required
Account
object
An account object contains the customer account related properties
5 properties 4 required
NumberAndFinancialInstitution
object
Customer account number and Financial Institution (Bank) information
2 properties 2 required
AlternateAccountIdentifier
object
An alternate form of identifier that can be used to identify the customer account
2 properties 2 required
AccountType
string
The type of account
AccountIdentifier
object
Contains account number and financial institution to uniquely identify a customer account
2 properties 2 required
FinancialInstitution
object
Financial Institution identifier
3 properties 2 required
IdType
string
The Id type of the Bank or Financial Institution
BalanceInquiry
object
Balance schema used to provide the inquiry criteria based on which balance information is retrieved
4 properties 1 required
AccountBalances
object
2 properties 2 required
AccountBalance
object
Account balance information
2 properties 2 required
Balance
object
3 properties 3 required
ISOCurrencyCode
string
ISO 4217 Alpha-3 Currency Code
SignedDecimal
string
A String representation of a (potential) decimal number Follows ISO 4217 standards to represent minor unit currencies
Cursor
object
5 properties 2 required
CursorId
string
For selecting a cursor when using pagination
PageSize
integer
For pagination, the total number of results to return
Error
object
5 properties 1 required
ErrorContext
object
The following is a list of error codes that may be returned and their associated rule definitions | Error Code | Definition | | --- | --- | | 10001 | Mandatory…
4 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-blockchain-deposit-account-balances-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Digital Onboarding API
Consumer Profile Management API
Tokenization API
Reporting API
Notifications API
Request to Pay via QR Code API
Checkout API
Dispute Management API
Accounts API
Alerts and Decisioning API
Product Configuration API
Recipients API
Where this information came from

This is an independent, third-party profile of Blockchain Deposit Account Balances 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.