Build e-invoicing into your ERP

Your first invoice in one request

Your ERP sends its own invoice JSON. A mapping your company certifies turns it into a PINT-OM e-invoice. The examples use fictitious data.

1. Certify a mapping for your ERP’s invoice data in the Fawtir web app.
2. Create an ERP_INGESTION key. It can send documents and read nothing.
3. Send the invoice with one POST. A valid document is answered 202 Accepted.
4. Read its status with an OAuth client that holds only invoice.read.

Follow the quick start

Send

Push an invoice

curl -i -X POST "{BASE_URL}/api/v1/invoices" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: fawt_sk_<your-key>" \
  -H "Idempotency-Key: waha-inv-000145-v1-7f3c9a2e" \
  -H "X-Correlation-Id: 3f1c2a9e-7b4d-4c1a-9e2f-6a8b0c4d2e17" \
  --data @invoice-INV-2026-000145.json

202 Accepted

Response (abridged)

{
  "id": "invc_01JCQ7Z8K4M2N6P9R3T5V7X9YB",
  "invoice_uuid": "3f6d2a9e-8c41-5b7e-9a12-6c0e4f8b2d17",
  "document_kind": "STANDARD_INVOICE",
  "state": "QUEUED",
  "peppol_send": { "target_participant": "0248:OM1999000202", "status": "queued" },
  "tdd": { "status": "queued", "sla_deadline": "2026-11-10T06:30:04Z" },
  "source": {
    "external_document_id": "ERP-INV-000145",
    "external_version": "1",
    "disposition": "ACCEPTED"
  }
}

Read status

Read the live status

curl -s "{BASE_URL}/api/v1/invoices/invc_01JCQ7Z8K4M2N6P9R3T5V7X9YB" \
  -H "Authorization: Bearer <access-token>"

Three ways to connect

All three use the same certified mapping and the same validation, and produce the same PINT-OM document.

API Push

Your ERP calls Fawtir’s REST API, one document per request, with an ERP_INGESTION key. Invoices, credit notes, debit notes and self-billed documents. The usual choice.

Managed Pull

Fawtir calls your ERP’s HTTPS JSON endpoint on a schedule and collects new tax invoices with a cursor. For ERPs that already expose invoices over REST.

Bridge Upload

A person signed in to Fawtir uploads one exported invoice, as JSON or XML, up to 4 MiB. For low volume, a pilot, or recovering a single document.

What Fawtir does

Converts with your mapping, validates in five layers, builds the PINT-OM e-invoice, delivers it over Peppol AS4 and reports the Tax Data Document.

Everything you need

Authentication API keys to push, OAuth clients to read, and every authentication error.

API reference Every endpoint an integration uses, with requests and responses.

ERP data mapping How your ERP fields become PINT-OM, and the rules Fawtir enforces.

Invoice lifecycle Statuses, Peppol delivery, recipient responses and tax data reporting.

Error reference Every error code, what it means and what to do.

Invoice corrections Credit notes, debit notes and fixing rejected documents.

Webhooks Optional event notifications, and polling.

Platform limits Sizes, rate limits, precision, dates and numbering.

Ready to go live?

Build in the sandbox, pass the TEST checklist, then follow the production go-live steps.

Sandbox (TEST) Where you build and test: access, what to ask first, good habits.

TEST checklist The scenarios to pass before you go live.

Production go-live Moving from TEST to production safely.