Guides
Pagination & freshness
Read stored data deliberately. A successful response can still describe an incomplete history or an older balance.
Follow the cursor
Transaction and institution lists return next_cursor. Pass it as cursor on the next request, keeping the same account, dates and other filters. Stop when it is null.
Transaction pages accept limit from 1 to 500. Resource restrictions are applied before pagination, totals and enrichment, so you only see data allowed by your key.
const headers = { Authorization: `Bearer ${process.env.BANKING_API_KEY}` };
let cursor: string | null = null;
do {
const url = new URL('https://api.bankmcp.app/v1/accounts/ACCOUNT_ID/transactions');
url.searchParams.set('limit', '100');
if (cursor) url.searchParams.set('cursor', cursor);
const response = await fetch(url, { headers });
if (!response.ok) throw new Error(`Banking returned ${response.status}`);
const page = await response.json();
// Store the complete page, including its coverage and freshness metadata.
console.log(page);
cursor = page.next_cursor;
} while (cursor);
Check freshness and coverage
Inspect retrieved_at, coverage, warning and complete where present. Reads do not contact the bank. A refresh or history import queues explicit work; receiving a job response does not mean the import has finished.
Do not present a partial page or incomplete history as a complete spending total. Linked wallet details can be absent for account-restricted keys.
Preserve money accurately
Amounts are exact decimal strings. Use decimal arithmetic and keep currencies separate. Avoid converting money to floating-point numbers or adding different balance types together.