What format does the API return?

JSON with structured transaction data: date, description, amount, debit/credit, and AI-assigned category. Optional export to CSV, Excel, QIF, OFX, or QBO.

Which banks are supported?

Banks worldwide are supported as long as the statement comes as a PDF. Text-based and scanned documents both work, and OCR is handled automatically when needed. The important constraint is statement quality, not a pre-approved bank list.

How do I get an API key?

Sign up, go to the Developers page, and create an API key instantly. No approval process — your key works immediately with your plan's limits.

What are the rate limits?

API usage counts against your plan and follows the same page-based limits as the web app. Treat it as a document-processing API rather than a per-request toy endpoint, especially if you plan to handle multi-page statements at volume.

Can I export directly to accounting formats?

Yes. A single API call can return JSON, CSV, Excel, QIF, OFX, or QBO. No intermediate processing needed — go from raw PDF to accounting-software-ready file instantly.

All statements are processed over HTTPS. Uploaded files are processed in memory and immediately discarded — never stored on disk, never shared. Only the structured transaction data is returned in the API response.

Bank Statement API — Parse & Analyze PDFs Programmatically (2026)

Bank statement API

Send a PDF — get back structured JSON , AI categories , and export formats via one REST call.

Get Your API Key

REST API JSON output 19 categories

EncryptedPDF never storedNo signup

Integration

One endpoint, structured data back

request.sh

curl -X POST https://mybankstatementanalysis.com/api/analyze \
  -H "Authorization: Bearer mbsa_YOUR_KEY" \
  -F "file=@statement.pdf"

// Response
{
  "transactions": [
    { "date": "2026-01-15", "description": "WHOLE FOODS", "amount": -87.32, "category": "Groceries" }
  ],
  "summary": { "total_in": 4200.00, "total_out": 3156.78 }
}

Capabilities

What the API does

One POST request. Structured data back. No PDF library, no OCR setup, no AI on your end.

Extract transactions

Parse any bank PDF to structured JSON — date, description, amount, debit/credit flag. Scanned or digital PDFs handled automatically.

AI categorization

19 spending categories assigned automatically. Groceries, dining, transport, housing, subscriptions, and more — no training needed.

Export formats

Get results as JSON, or export to CSV, Excel, QIF, OFX, or QBO — all from the same API call. One endpoint, any format.

Bank statement PDF being parsed through AI into structured JSON data

POST /api/analyze→ JSON

How it works

PDF in, structured data out

Send any bank statement PDF to a single endpoint. Our pipeline handles text extraction (or OCR for scanned documents), parses every transaction, and runs AI categorization — all in one request.

You get back clean JSON with date, description, amount, debit/credit flag, and one of 19 spending categories per transaction. No PDF libraries to install, no OCR to configure, no AI models to manage.

Built for every builder

From solo devs to enterprise platforms — integrate bank statement parsing in minutes.

Fintech apps

Auto-categorize transactions and surface spending insights inside your product.

Accounting tools

Import statements directly — skip manual data entry and map to your ledger.

Loan underwriting

Extract income and expense patterns from applicant statements in seconds.

Personal finance

Build your own bank statement analyzer on top of our parsing and AI engine.

AI classifying bank transactions into 19 spending categories via API

Performance

<5s/page

Average processing time per page — including OCR, parsing, and AI categorization

Why developers choose a bank statement parsing API

Building bank statement parsing from scratch means maintaining aPDF extraction layer, anOCR pipelinefor scanned documents, and anAI classification modelthat understands financial transaction descriptions. That's three complex systems to build, test, and maintain — before you write a single line of product code.

Our API replaces all three with one HTTP call. Send a PDF, get back structured JSON with every transaction extracted and categorized into 19 spending categories. The API handles 500+ bank formats worldwide, both digital and scanned PDFs, and normalizes messy transaction descriptions into clean, consistent labels. For fintech apps, this means faster time-to-market. For loan platforms, it means automated underwriting without manual document review.

Authentication is simple — Bearer tokens tied to your plan. No OAuth flows, no API key rotation requirements. All requests are encrypted over HTTPS, and uploaded files are processed in memory andimmediately discardedafter extraction — nothing is stored. The sameREST endpointsupports direct export to CSV, Excel, QIF, OFX, and QBO — meaning your integration can go from raw PDF to accounting-software-ready file in a single call.

Integration fit

When the API is the right choice

Product teams

Use the API when statement parsing should be part of your own workflow, not a manual back-office step.

Document pipelines

Use it when uploaded PDFs already flow through underwriting, bookkeeping, or verification systems and need structured output in the middle.

Multi-format output

Use it when one input must feed multiple destinations like JSON for your app and CSV or QBO for downstream teams.

Not for one-off use

If you only need a manual upload once in a while, the web app or converter pages are usually the simpler entry point than API integration.

Method & Coverage

Supporting pages for teams evaluating the API

These pages explain OCR quality, extraction assumptions, supported statement types, and the workflows behind the API so integration decisions are grounded in real document behavior.