Document extraction API

Document data your systems can rely on.

Start with a PDF invoice. exdata extracts the fields that matter, keeps the evidence visible, and returns clean JSON for accounting, archive, ERP, and back-office systems.

Get API access Developer workflow

supplier-invoice.pdf PDF invoice uploaded

Ready

Document number INV-2026-1048 · found near invoice title

Extracted

Total payable EUR 1,079.50 · reverse charge VAT

Extracted

Payment details IBAN, BIC, due date, payment reference

Extracted

Tax breakdowns Reverse charge, EU VAT 0.00, taxable amount

Extracted

extraction.json

{
  "type": "invoice",
  "document_number": "INV-2026-1048",
  "sender_name": "Meyer Supply GmbH",
  "sender_country_code": "DE",
  "recipient_name": "Vistula Retail sp. z o.o.",
  "recipient_country_code": "PL",
  "issue_date": "2026-05-14",
  "payment_due_date": "2026-06-14",
  "net_amount": "1079.50",
  "tax_amount": "0.00",
  "gross_amount": "1079.50",
  "currency": "EUR",
  "tax_breakdowns": [
    {
      "taxable_amount": "1079.50",
      "tax_amount": "0.00",
      "tax_rate": "0.00",
      "taxability": "taxable",
      "tax_collection_mechanism": "reverse_charge",
      "tax_exemption_reason": "Reverse charge"
    }
  ],
  "cross_border_tax_treatment": "intra_eu_b2b_reverse_charge",
  "iban": "DE89370400440532013000",
  "payment_reference": "INV-2026-1048"
}

/api/v1 PDF-first document API

mode: test Sandbox-first rollout

X-Signature Signed webhooks

OpenAPI OpenAPI contract

Why teams use it

Less manual keying. Fewer brittle handoffs.

Teams usually do not need another OCR dump. They need invoice numbers, suppliers, totals, tax rows, due dates, and payment details in the system that runs the workflow.

exdata is built for a controlled path from sample PDFs to production automation: test the result, inspect the evidence, then connect the downstream system.

Start with the common case

Process PDF invoices first, then add scans, email attachments, XML, and e-invoices through the same API when the workflow grows.

Explore product

Return fields software can trust

Extract document numbers, parties, IBAN/BIC, due dates, totals, VAT IDs, tax rows, cost centers, and references as normalized JSON.

See use cases

Keep rollout observable

Test with sample PDFs, inspect the result, and move to production only when polling, webhooks, and mapping are ready.

Review credits

Explore

Go deeper where your question starts.

How it works How documents become structured JSON. Inputs, extraction paths, normalized fields, workspace visibility, and account controls. Developers How to build and support an integration. Idempotent uploads, polling, webhooks, test mode, OpenAPI, and error handling. Use cases Where exdata fits by sector. Accounting teams, archives, ERP integrators, finance teams, and service providers. Security How rollout, support, and controls are handled. Data boundaries, retention, signed webhooks, roles, audit context, and support signals.

Production workflow

The operating layer around extraction.

Developers get a clean API. Operations teams still get the states, previews, run metadata, blocked reasons, and account controls they need when automation meets real documents.

Product details API docs

FormatsMulti-format processing: PDFs first, with scans, images, text, HTML, Word files, XML, EDI-style payloads, and email-based invoice flows available when needed.
TestingSandbox mode: Test-mode tokens exercise the same endpoints, validation, idempotency, webhooks, and error envelope without spending live credits.
ReviewExtraction visibility: See document status, previews, extracted metadata, run versions, failure reasons, and API-shaped JSON in the workspace.

Controlled rollout

For teams that need document automation to be predictable.

Developer teams get a stable API while operations can inspect extraction runs, blocked documents, and source previews.

Developer-owned workflows

Finance and operations teams can move invoice handling into workflows with status, audit context, and JSON outputs.

Operational document pipelines

Account tokens, test mode, usage separation, and top-up controls support cautious rollout before larger production volume.

Controlled integration rollout

Start with one document

Create a token, upload a real sample, and review the JSON your workflow can use.

Get API access Integration path