API key auth · scoped permissions

Bank Statement API

Upload bank statements and get back structured, labeled transactions — programmatically. Built for lenders, underwriters, and fintech workflows that need clean data, not PDFs.

curl -X GET "https://statements.finopsbricks.com/api/v1/transactions" \
  -H "api-key: fob_stm_xxxxxxxxxxxx" \
  -H "api-secret: xxxxxxxxxxxxxxxx"

Every key is scoped to one organization, with read/write permissions per resource — full access, read-only, or a custom matrix.

Core resources

/api/v1/statements

Upload, list, and retrieve bank statements

/api/v1/transactions

Query extracted, labeled transactions

/api/v1/accounts

Manage bank accounts and identifiers

/api/v1/rules

Automated categorization rules

/api/v1/categories

Read-only category aggregates

/api/v1/entities

Read-only counterparty aggregates

/api/v1/reports

Computed financial reports (balance, cashflow)

Structured, not raw text

Date, amount, particulars, running balance — already extracted and deduplicated, not a PDF dump for you to parse again.

Scoped, revocable access

Full access, read-only, transactions-only, or a custom permission matrix per key. Set an expiry, rotate anytime.

LLM-ready

The same data is reachable through the fobs CLI and a Claude skill, so you can ask natural-language questions without building your own integration.

CLI access

The fobs CLI wraps the same API for terminal-first workflows — scripts, pipelines, ad-hoc queries.

CLI docs →
Event notifications

Webhooks for statement, transaction, account, and rule events are available — HMAC-signed, per-event opt-in. Configure one from your org's Settings, or keep polling the API instead.

See the webhook docs →

Start building

$5 free credit, no card required. Create an org, generate an API key, and start querying.