API reference / Accounts
GET
/v1/accountsList accounts
Requires accounts:read. Resource restrictions also apply. Read account details.
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' \
-H "Authorization: Bearer $BANKING_API_KEY"
const response = await fetch('https://api.bankmcp.app/v1/accounts', {
headers: {
Authorization: `Bearer ${process.env.BANKING_API_KEY}`,
},
});
if (!response.ok) throw new Error(`Banking returned ${response.status}`);
const data = await response.json();
Parameters
bank_idqueryoptionalstring — Bank ID from list_banks, e.g. "DE:N26" (country code and bank name).
include_closedqueryoptional"true" | "false"
Response
200 · application/json
environment"sandbox" | "production"requiredaccountsarray<object>requiredShow accounts schema
idstringrequiredbank_idstringrequiredBank ID from list_banks, e.g. "DE:N26" (country code and bank name).
namestringrequiredproductstring | nullrequiredShow product schema
Option 1: string
string
Option 2: null
null
bankobjectrequiredShow bank schema
namestringrequiredcountrystringrequiredISO 3166-1 alpha-2 country code, e.g. DE
currencystring | nullrequiredShow currency schema
Option 1: string
string
Option 2: null
null
iban_last4string | nullrequiredShow iban_last4 schema
Option 1: string
string
Option 2: null
null
closedbooleanrequiredconsent_expires_atstringrequiredconsent_expiredbooleanrequiredErrors
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.