The e-invoice API for your app.
Your ERP, invoicing tool or SaaS must output XRechnung, Peppol BIS or Factur-X? Send JSON, get compliant XML back — validated. Receiving e-invoices? Send the XML or PDF, get JSON.
Endpoints
| Method | Path | Input | Result |
|---|---|---|---|
| POST | /v1/parse | XML or PDF | Invoice as JSON, detected format, validation report |
| POST | /v1/render | XML or PDF | Readable, printable HTML page |
| POST | /v1/validate?profile= | XML, PDF or JSON | Validation report (built-in check, optionally official KoSIT) |
| POST | /v1/convert?to= | Invoice JSON | XML in the target format |
| POST | /v1/transform?to= | XML or PDF | The same invoice in another format |
| GET | /v1/formats | — | Supported output formats |
Read an e-invoice in one call
curl -X POST "https://invoicebridge-e-invoice-api.p.rapidapi.com/v1/parse" \
-H "X-RapidAPI-Key: YOUR_RAPIDAPI_KEY" \
-H "X-RapidAPI-Host: invoicebridge-e-invoice-api.p.rapidapi.com" \
-H "Content-Type: application/xml" --data-binary @invoice.xml
Send XML as application/xml, a ZUGFeRD / Factur-X PDF as application/pdf, JSON as application/json. Up to 20 MB per document.
Built for compliance work
Totals calculated
Omit line amounts, VAT breakdown and totals in your JSON — they are calculated with EN 16931 rounding.
No silent data loss
Conversions report every element the target format cannot carry.
Official validation
The KoSIT validator with the XRechnung 3.0, EN 16931 and Peppol BIS 3.0 rules runs next to the API.
Not stored
Documents are processed in memory in Azure West Europe and discarded after the response.
Plans
Billed by RapidAPI. Start free, upgrade when you go live.
Basic
10 requests / month
Pro
1,000 requests / month
Ultra
10,000 requests / month
Mega
30,000 requests / month
Current prices and limits are always those shown on RapidAPI. Need a direct contract without RapidAPI? Contact us.