Private API Pilot

Convert bank statement PDFs into validated JSON.

Build statement conversion into your own product. Submit digital or scanned PDFs and receive normalized transactions, page scope, balance-review signals, and an explicit delivery state.

Apply for API Pilot

Built for accounting platforms, lenders, and workflow software. The API is not generally available; accepted teams enter a paid, scoped pilot.

v1 request preview

curl https://api.bankscanpro.com/v1/jobs \
  --request POST \
  --header "Authorization: Bearer $BANKSCANPRO_API_KEY" \
  --header "Idempotency-Key: loan-application-1842" \
  --form "file=@statement.pdf" \
  --form 'options={"pages":"all","result_format":"canonical_json"}'

Asynchronous job contractStatus: preview

Designed for products that need repeatable, reviewable statement data.

Accounting SaaSLoan underwritingBookkeeping automationDocument workflows

Integration path

One asynchronous flow, with uncertainty kept visible.

The pilot contract is intentionally small. Your application should not need to understand BankScanPro's internal extraction pipeline to decide whether a result can move downstream.

Read the developer preview

01
Prepare the request
Choose the page scope, client reference, and result options for a digital or scanned PDF.
02
Submit a conversion job
Send the PDF and options in one authenticated request with an idempotency key for safe retries.
03
Wait for a terminal status
Poll the job or receive a signed webhook when processing reaches a deliverable or review state.
04
Retrieve structured results
Read normalized transactions, page scope, validation checks, warnings, and allowed exports.

BASE delivery contract

A result can be useful without pretending it is complete.

BankScanPro separates extracted rows from the decision to deliver them automatically. Page coverage, balance checks, source evidence, and completeness anchors remain machine-readable.

complete

The requested page scope passed the automatic delivery gates. Review signals remain available.

partial

Source-backed rows are available, but the supplied document or requested scope is incomplete.

needs_review

The result is retained for review instead of being silently promoted to a reliable conversion.

failed

No safe result is available. The error response explains whether the request can be retried.

Page-scope evidence

Requested, processed, and delivered pages remain explicit.

Canonical fields

Stable transaction, account, period, and validation shapes.

Terminal notifications

The v1 contract includes signed webhook delivery for pilot integrations that need it.

Commercial model

Start with a paid acceptance pilot. Scale after the workflow is proven.

API usage is separate from web subscriptions. We use physical PDF pages as the value metric and document retry, failure, and overage rules in each pilot agreement.

Pilot

Accepting applications

Teams validating one production workflow

Paid pilot with an agreed page allowance

Integration and acceptance workshop
Representative sample-corpus review
Canonical JSON result contract
Shared launch and support channel

Growth

Designed with pilot customers

Products with recurring statement volume

Monthly minimum, included pages, and overage

Higher concurrency
Signed completion webhooks
Usage and credit reporting
Operational support targets

Enterprise

Scoped by agreement

Regulated or high-volume deployments

Custom volume and service agreement

DPA and security review
Custom retention requirements
Named-layout onboarding
Contracted support and service terms

Security questions belong before production data.

Pilot scoping covers authentication, data flow, retention, logging exclusions, deletion, DPA needs, and webhook verification.

API FAQ

Is the BankScanPro API generally available?+

No. The API is currently a private, paid pilot for a small number of accounting, lending, and workflow-software teams. The web converter remains generally available.

How is API usage priced?+

The pilot uses physical PDF pages as the usage metric. Each agreement defines its included page allowance, handling of retries and failed jobs, and any monthly minimum or overage.

Does the pilot support scanned statements?+

The underlying BankScanPro conversion system handles both digital and scanned PDFs. Pilot acceptance still depends on representative sample statements, layout mix, volume, and review requirements.

What happens when a result is uncertain?+

The API contract exposes complete, partial, needs_review, and failed outcomes. It does not silently promote an incomplete or weakly supported result to complete.

Are web-plan pages shared with API usage?+

No shared entitlement is promised during the pilot. API allowances and commercial terms are defined separately from self-serve web plans.

Can we review security and retention before sending data?+

Yes. Qualified pilot customers can review the data flow, retention requirements, DPA needs, authentication contract, and operational responsibilities before production samples are accepted.

Apply

Bring a real workflow, not a generic API wishlist.

We prioritize teams with representative statements, a defined downstream consumer, measurable monthly volume, and someone available to review pilot results.

No client statement data is required in this form.
The first conversation defines acceptance and security needs.
Production access follows a paid, scoped agreement.

Application 1 of 2