1. Upload
POST /api/v1/developer/uploads with the PDF as the multipart field "file" and the header Authorization: Bearer <your key>. Returns 202 with an upload id.
Bank statement to JSON
Your app needs transactions, and your users' banks send PDFs. Drop one here to see the JSON, then call the API to get the same JSON from your own code: no templates per bank, no webhooks to host.
Goes in
A bank or credit-card statement PDF, digital or scanned, up to 20 MB, from the web or the API
Comes out
statement.json: account details, a transactions array and a balance check
{
"date": "2026-10-02",
"description": "Acme Payroll",
"credit": 3200,
"debit": null,
"balance": 5450,
"reference": "PPD 1002",
"classification": "ACME PAYROLL"
}This is the structure the worker stores and you download, filled with a four-line sample statement. Amounts are numbers, missing values are null, dates are YYYY-MM-DD strings.
{
"bank_name": "Example Bank",
"account_holder": "Jordan Lee",
"account_number": "XXXX4821",
"currency": "USD",
"statement_period": {
"from": "2026-10-01",
"to": "2026-10-31"
},
"opening_balance": 5450,
"closing_balance": 4766.61,
"transactions": [
{
"date": "2026-10-02",
"description": "Acme Payroll",
"credit": 3200,
"debit": null,
"balance": 5450,
"reference": "PPD 1002",
"classification": "ACME PAYROLL"
},
{
"date": "2026-10-03",
"description": "Amazon",
"credit": null,
"debit": 64.99,
"balance": 5385.01,
"reference": null,
"classification": "AMAZON"
},
{
"date": "2026-10-05",
"description": "City Electric Co",
"credit": null,
"debit": 118.4,
"balance": 5266.61,
"reference": "ACH 88213",
"classification": "CITY ELECTRIC CO"
},
{
"date": "2026-10-07",
"description": "Rent - Oak Street",
"credit": null,
"debit": 500,
"balance": 4766.61,
"reference": "CHK 1043",
"classification": "OAK STREET RENTALS"
}
],
"balance_check": {
"is_valid": true,
"opening_balance": 5450,
"closing_balance": 4766.61,
"expected_closing": 4766.61,
"discrepancy": 0,
"total_credits": 0,
"total_debits": 683.39,
"rows_verified": 3,
"rows_failed": 0,
"failed_rows": [],
"warnings": [
"All balances verified successfully"
]
}
}Sample data from a made-up statement, not a real account.
Step 1
Upload a PDF on this page and open the JSON tab of the preview.
Step 2
Sign in and name a key in the developer console. The secret is shown once.
Step 3
POST the PDF, poll the upload until it is done, then fetch the result.
Processing is asynchronous. Upload returns an id; poll that id every few seconds until its status is done; the result holds the statement as JSON and as CSV.
POST /api/v1/developer/uploads with the PDF as the multipart field "file" and the header Authorization: Bearer <your key>. Returns 202 with an upload id.
GET /api/v1/developer/uploads/:id until status is done or failed. Every two or three seconds is enough; most single statements finish in seconds.
GET /api/v1/developer/uploads/:id/result returns outputJson (the structure above), outputCsv and rowsDetected.
curl -X POST https://parsemystatement.com/api/v1/developer/uploads \ -H "Authorization: Bearer $PSM_API_KEY" \ -F "[email protected]" curl https://parsemystatement.com/api/v1/developer/uploads/$UPLOAD_ID/result \ -H "Authorization: Bearer $PSM_API_KEY"
Keys are created in the developer console; every endpoint is in the API and MCP docs.
bank_name, account_holder, account_number, currency, statement_period (from, to), opening_balance, closing_balance, a transactions array (date, description, credit, debit, balance, reference, classification) and balance_check.
Yes. Create a key at /developers, POST the PDF to /api/v1/developer/uploads, poll /api/v1/developer/uploads/:id, then GET its /result for the JSON and CSV. The full reference is at /docs/api.
Numbers. Credit and debit are positive floats, balance can be negative, and any value the statement does not show is null.
Whether each running balance equals the previous balance plus credits minus debits. rows_failed and failed_rows point at the rows that do not add up, which is where to look first.
Yes. Besides the REST API there is an MCP server, documented with the API at /docs/api.
No. The parser is not template-based; every bank's statement comes back in the same JSON shape.
Create keys, see request logs, rotate or revoke keys.
Endpoints, auth, schema and MCP tools.
Text extraction, OCR, row extraction and the balance check.
The same rows as a CSV file.
The same rows as an .xlsx workbook.
How AI OCR tools compare on bank statements.