JSON Export

Bank statement to JSON, structured

A nested array of transaction objects with statement-level metadata — built for developers wiring bank data into an app, database, or internal API.

How It Works

1

Upload via dashboard or API

Send a PDF through the web dashboard, or POST it directly to the conversion endpoint for automated workflows.

2

Transactions are structured

Each transaction becomes its own object with typed fields, nested under statement-level metadata like bank name and statement period.

3

Get a JSON array back

Consume the response directly in your app, drop it into a database, or route it through Zapier or Make.

What's in the JSON file

Columns / fields

  • date
  • description
  • debit
  • credit
  • balance
  • type
  • meta.bank
  • meta.periodStart
  • meta.periodEnd

Works well with

Internal APIsZapier / MakeCustom dashboardsSQL / NoSQL databases

Transaction fields are typed (numbers as numbers, dates as ISO strings) and nested under a metadata object per statement, so you're not re-parsing strings on the receiving end of an integration.

Convert your statement to JSON

API access included on Pro and Enterprise plans.

Start ConvertingView API Docs
Got Questions?

Frequently Asked Questions

We accept PDF bank statements from any bank. You can also paste screenshots or images of statements.
Yes. All files are encrypted during upload and processing. We delete your files immediately after conversion and never store banking credentials.
Date, description, debit/credit amounts, running balance, and transaction type. Column headers are standardized for easy import into accounting software.
Free accounts can convert statements up to 50 pages. Paid plans support unlimited pages and bulk conversion.
Yes. Paid plans include bulk conversion. Upload multiple PDFs and get individual JSON files for each statement. Learn more

Still have more questions?

Contact Support