API reference / Accounts
GET
/v1/accounts/{id}/balancesRead balances
Requires balances:read. Resource restrictions also apply. Read balances.
Reads use stored data and do not refresh the bank.
Request examples
These examples use HTTP directly. Keep API keys on your server.
curl 'https://api.bankmcp.app/v1/accounts/RESOURCE_ID/balances' \
-H "Authorization: Bearer $BANKING_API_KEY"
const response = await fetch('https://api.bankmcp.app/v1/accounts/RESOURCE_ID/balances', {
headers: {
Authorization: `Bearer ${process.env.BANKING_API_KEY}`,
},
});
if (!response.ok) throw new Error(`Banking returned ${response.status}`);
const data = await response.json();
Parameters
idpathrequiredstring
Response
200 · application/json
environment"sandbox" | "production"requiredaccount_idstringrequiredretrieved_atstring | nullrequiredShow retrieved_at schema
Option 1: string
string
Option 2: null
null
source"stored" | "live"requiredwarningstringbalancesarray<object>requiredShow balances schema
balance_typestring | nullShow balance_type schema
Option 1: string
string
Option 2: null
null
namestring | nullShow name schema
Option 1: string
string
Option 2: null
null
balance_amountobjectrequiredShow balance_amount schema
amountstringrequiredExact decimal amount as a string
currencystringrequiredISO 4217 currency code
reference_datestring | nullShow reference_date schema
Option 1: string
string — Calendar date (YYYY-MM-DD)
Option 2: null
null
Errors
Errors contain error, code and an optional action. Read the error and retry guide.
| Status | Code |
|---|---|
| 400 | INVALID_INPUT |
| 401 | INVALID_API_KEY |
| 403 | INSUFFICIENT_PERMISSION |
| 404 | NOT_FOUND |
| 409 | CONFLICT |
| 413 | REQUEST_TOO_LARGE |
| 429 | rate_limit.feature |
| 500 | REQUEST_FAILED |
| 502 | INVALID_RESPONSE |
| 503 | UNAVAILABLE |
Try this request
Sent directly to https://api.bankmcp.app. Your key stays in this page’s memory and is never saved.