Bank statement parsing API documentation
StatementBear turns a bank or credit card statement into JSON. Send a PDF, a scan, a phone photo or a CSV export and get back every transaction, the account it belongs to, a check that the figures reconcile and signs that the file was edited. No bank login and no account for your customer.
/api/v1/documentsThe request#
Send the file as a raw body or as a multipart part named file. A statement of up to 60 pages comes back in the same response. A longer one, or any file you would rather not wait for, goes with async=true and arrives by webhook.
POST /api/v1/documents HTTP/1.1 Host: statementbear.com Authorization: Bearer sb_live_... Content-Type: application/pdf Idempotency-Key: 6f1b1f22-9c62-4c0e-b6a4-1d0f5f0b6f5a <the PDF bytes> HTTP/1.1 200 OK Content-Type: application/json X-Billable-Pages: 3 { "id": "doc_...", "status": "succeeded", "accounts": [ ... ], "verification": { ... }, "authenticity": { ... } }
What you get back#
- Every transaction, with the date and payee line as printed, the payee's name, a positive amount, an explicit
directionand a category. - Every account in the file, kept separate. Some issuers bill a current account and three savings accounts on one statement.
- Totals per account and per month, beside the totals the issuer printed.
- Recurring payments: subscriptions, rent, loan repayments.
- A verification object holding our check of the extraction against the statement's own balances.
- Authenticity signals: the file was edited, modified after it was made, or sent before. See Authenticity signals.
More than one endpoint#
| Endpoint | Use it to |
|---|---|
POST /api/v1/documents | Send a file. See Documents. |
GET /api/v1/documents/{id} | Fetch a result, in any state, for as long as your retention period. |
POST /api/v1/collections | Send an applicant a hosted upload link. See Collect statements from applicants. |
POST /api/v1/mcp | Let an AI agent read statements with your key. See MCP servers. |
Every endpoint, schema and webhook is described in OpenAPI 3.1 at statementbear.com/openapi.json. Generate a client from it or import it into your API tool.
What it does not do#
- Score or decide. You get the rows and the signals. Affordability, risk and eligibility are yours.
- Create an account for your customer. The person whose statement it is never hears from us.
- Keep the file you send. A file sent directly is read and discarded. Only the result is stored, for your retention period. See Security and data retention.
- Prove a statement is genuine. Authenticity signals say what to look at. A person decides.
When to use it#
Open Banking needs the account holder present, consenting, and banking with a covered institution. Mortgage files, SME lending, tenant screening, immigration and legal disclosure still run on statements the applicant hands over. Use this for those. Plenty of customers run both.
What it costs#
$0.08 for every page of a document that reads successfully, and $0.05 for every page past 50,000 in a calendar month. The first 200 pages are free and need no payment method. Failed reads and errors are free. See Pricing and billing.