FFolioDEMO
RECEIPT & EXPENSE DATA API

Every receipt.
Structured data, at scale.

One API that turns photos of receipts, tickets and invoices into validated expense data. Send one image or a batch of hundreds and get clean JSON back, for expense apps, accounting tools and data pipelines.

⇉ Batch API⌁ Signed webhooks⌘ REST & MCP
EVERY EXTRACTION, READY TO REVIEWWorkspace preview
Folio document workspace with travel expenses and a taxi receipt beside its extracted fields
Every document also lands in a review workspace, so your team can check what the model read.REVIEW WORKSPACE
Built around the documents
you actually work with.
↗ Flight tickets
⌁ Taxi receipts
▤ Hotel invoices
⊕ Everyday expenses
01 / WHO BUILDS ON FOLIO

One data layer.
Many products.

Folio does the extraction so your product does not have to. You keep the user experience; we return the data.

▤

Expense management apps

Add receipt scanning to your expense or reimbursement product without building or training a model.

▧

Accounting & bookkeeping

Turn the photos your clients send into supplier, date, total, VAT and tax ID fields.

⇉

Data collection pipelines

Process image archives in batches, with your own reference on every document.

⌘

AI agents

Give an agent an MCP server with scoped tools to extract, look up and export.

Three mobile app screens showing recent expenses, camera capture, and editable receipt data

Prefer an app? It comes with every plan.

01

Capture

Upload a photo from the web panel, or send it through the API.

02

Review

Check amounts, dates and supplier details against the original. Missing fields stay visible.

03

Export

Only confirmed expenses export, as CSV or through the API.

See a sample extraction ↓
03 / SEE THE OUTPUT

Messy paper.
Useful data.

Choose a sample and see how a document becomes a reviewable record. This demo uses illustrative data, not live OCR.

⌁

TAXI MADRID

SAMPLE DOCUMENT · NOT A REAL RECEIPT

TOTAL

Thank you for your journey.

THE ORIGINAL

Structured. Ready to review.

Review required

JSON RESPONSE

Extraction does not establish whether a document is a valid tax invoice.

02 / BUILT FOR VOLUME

From one image
to thousands.

A REST API, a batch API and an MCP server. Scoped keys decide what each integration can do.

From document to JSON.

REST API
✓

Keep people in control.
Only a person can confirm a document in the workspace. There is no payment permission: no key can move money.

WHAT THE API GIVES YOU
⇉
Batch APIUp to 500 documents per request, by URL or base64
⌁
Signed webhooksbatch.completed, signed with HMAC-SHA256
↺
Idempotency keysA retried request never processes a document twice
#
Your referencesclient_reference on every item, echoed back with the result
✓
Schema-validated JSONUnreadable fields come back null, never guessed
⏱
Rate limits per planCounted across every server, not per process

Batches are processed asynchronously: poll the batch or receive a webhook when it is done.

04 / PRICING

Start free.
Pay as you grow.

Every plan includes the REST API, batches, webhooks, the MCP server and the review workspace. Plans differ by volume.

Free

€0/ forever

No card needed

  • 50 documents a month
  • Batches of up to 25
  • API, webhooks and MCP
Get an API key ↗

Starter

€19/ month

+ VAT, billed monthly

  • 300 documents a month
  • Batches of up to 100
  • 60 requests a minute
Choose Starter ↗

Scale

Custom

Volume contract

  • From 10,000 documents a month
  • Volume price per document
  • 600 requests a minute
Talk to us ↗

Prices in euros, VAT not included. Paid plans open soon and will be billed through Stripe. Until then every account starts on Free and no card is asked for.

THE DETAILS MAKE THE DIFFERENCE

Clear data.
Clear boundaries.

01

Keep the source in sight

Pair extracted fields with the original document so reviewers can verify the details.

02

Leave room for uncertainty

Flag unreadable or missing fields instead of filling the gaps with guesses.

03

Make permissions intentional

Four scopes: documents:read, documents:write, expenses:read, expenses:write. A key only sees the tools it can call.

FROM RECEIPT TO DATA

Put receipt data
into your product.

Create a key, send your first batch, get JSON back.

Get an API key ↗Read the API docs