POST /v1/bank/statement · 1 cent per operation

Bank statement (CAMT.053 / MT940) to JSON, Excel or CSV

Read bank statements from online banking (CAMT.053/052/054, MT940) into transactions with counterparty, IBAN, purpose and SEPA references; checks the balances add up.

Try it

curl -X POST https://api.bigapi.dev/v1/bank/statement -H 'Authorization: Bearer $KEY' -F 'file=@auszug.xml' -F 'output=json'

New keys come with 100 free operations, no signup: curl -X POST https://api.bigapi.dev/v1/keys. Failed calls cost nothing.

Parameters

Name	Meaning
`file` required	Statement file as downloaded from online banking: CAMT XML (.xml) or MT940 text (.sta, .txt, .mt940). Not a PDF statement.
`output`	json for agents; xlsx with sheets 'Buchungen' and 'Übersicht'; csv with semicolons and decimal commas for German Excel. Allowed: `json`, `xlsx`, `csv` Default: json

Result and price

1¢ · 1 cent per operation

Returns application/json | spreadsheet | text/csv. Response headers carry the cost (X-BigAPI-Cost) and notes about your input (X-BigAPI-Warnings).

Good to know

Batch bookings (one entry, several payments) are split into single transactions when the bank lists them.
Amounts are signed: money in is positive, money out is negative.
We check opening balance plus transactions against the closing balance. If they do not match, X-BigAPI-Warnings says so (balance_mismatch): a statement may be missing.

Errors your agent should handle

`400 not_a_statement`	Neither CAMT nor MT940, or XML with a DOCTYPE.
`422 not_a_statement`	A PDF statement. Download the CAMT or MT940 file from your online banking instead.

From an agent (MCP)

Connect BiGapi as an MCP server: https://api.bigapi.dev/mcp (hosted) or npx -y @bigapi/mcp (local). Then ask in plain words; the agent finds bank_statement on its own.

Turn this bank statement into an Excel sheet and tell me which payments came in.

More: all guides · API docs · llms.txt