Parse Invoice PDF API

Parse invoice PDFs without building a PDF stack.

Send an invoice PDF to Parseify and receive normalized JSON for AP, bookkeeping, and expense automation. No layout engines, no template library, no OCR ops burden.

Request
curl -X POST https://api.parseify.app/api/v1/documents \
  -H "X-Api-Key: bnj_live_xxxxxxxxxxxxxxxxxxxxxx" \
  -F "file=@invoice.pdf"
Response
{
  "vendor": "Byte Office Supplies",
  "invoiceNumber": "INV-2026-0419",
  "date": "2026-04-19",
  "totalAmount": 499.13,
  "vatAmount": 86.63,
  "currency": "EUR",
  "lineItems": [
    { "description": "A4 paper box", "quantity": 3, "unitPrice": 29.90, "totalPrice": 89.70 }
  ]
}

Built for invoice PDF pipelines

PDF-First Workflows

Accept supplier PDFs from email or portals and parse them into JSON your ERP can post.

Schema-Stable Output

The same field names on every response keep your parsers and validators simple.

Minutes to Integrate

One multipart upload and an API key — works from curl, Node, Python, or .NET.

Parse invoice PDF API, frequently asked questions

How do I parse an invoice PDF with an API?

Upload the PDF to Parseify's /api/v1/documents endpoint with your API key. The parse invoice PDF API returns structured JSON with vendor, totals, tax, and line items — not a page of OCR text.

Does the parse invoice PDF API handle multi-page invoices?

Yes. Multi-page PDF invoices are accepted (up to 20 MB) and returned in the same JSON schema as single-page files.

Do I need PDF templates to parse invoices?

No. Parseify is tuned for invoices and receipts out of the box. You do not define per-vendor PDF templates or train a model before first use.

What is the difference between parsing a PDF and converting it to JSON?

Parsing extracts business meaning from the PDF. Parseify returns that meaning as JSON fields your application can trust — see also convert invoice PDF to JSON for the conversion workflow.