BANKTRUST

API reference · v1

BANKTRUST API

The BANKTRUST API lets teams process PDF bank statements and receive reconciled, structured transaction data for accounting workflows. It is built for reviewable, reconciliation-first automation rather than blind extraction.

Access

API access is available for account-enabled workspaces. API keys are tied to a BANKTRUST account and should be used only from secure server-side systems.

Version
v1
Auth
X-API-Key header
Format
Multipart PDF upload

Authentication

API requests are authenticated with a secret API key associated with your BANKTRUST account.

  • Send your key in the HTTP header X-API-Key: YOUR_API_KEY.
  • Keep API keys out of frontend code, browser apps, mobile apps, screenshots, public repositories, and client-side logs.
  • Treat API keys like passwords. Rotate or revoke keys if they may have been exposed.

Create statement from PDF

Upload a single PDF bank statement and receive a processed statement record with parsed transaction data and reconciliation metadata. This API mirrors the same reconciliation-first workflow used in the BANKTRUST web application.

Endpoint

  • POST /api/v1/statements
  • Content-Type: multipart/form-data

Headers

  • X-API-Key – your BANKTRUST API key.
  • Content-Type – handled automatically by most HTTP clients when uploading form data.

Form fields

  • file – PDF bank statement file.
  • client_id – UUID of the client in your BANKTRUST workspace.

Response

  • Processed statement metadata.
  • Parsed transaction rows.
  • Opening and closing balance signals when available.
  • Reconciliation status and variance metadata.
  • Trust and review signals for downstream workflows.

Review-first design

BANKTRUST is designed to make statement processing observable and auditable. API outputs should be reviewed before they are used in bookkeeping, accounting, reporting, tax, or operational systems.

  • If a statement reconciles cleanly, outputs can support downstream accounting workflows with more confidence.
  • If a statement has missing data, unsupported formatting, scan quality issues, or reconciliation variance, your workflow should treat the result as needing review.
  • API consumers are responsible for maintaining appropriate approval, backup, and review controls.

Accounting workflows

API outputs can support downstream workflows such as CSV exports, QuickBooks-style import preparation, Xero-ready transaction workflows, internal review pipelines, and accounting-system posting flows where enabled in the account.

Support

For API credentials, implementation questions, account setup, or support, contact support@banktrustapp.com.