Converter API

No need to wait for the Converter API: the Parser API returns a canonical invoice JSON for every supported invoice, and the Creator API accepts it directly as input. Two API calls give you a complete conversion today – in this example: XRechnung to ZUGFeRD.

1. 1Parse the source invoice – POST /api/v1/invoice/parse accepts XML or ZUGFeRD/Factur-X PDF (Base64) and auto-detects format and country.
2. 2Optionally validate – the validate endpoint checks the invoice JSON against country rules without consuming your quota.
3. 3Generate the target format – pass the invoice JSON unchanged to the target format's generate endpoint; set the ZUGFeRD profile via formatOptions.profile.

1# Works today – Parser + Creator API combined
2 
3# 1) Parse the source (auto-detects format & country)
4INVOICE=$(curl -s -X POST https://service.invoice-api.xhub.io/api/v1/invoice/parse \
5  -H "Authorization: Bearer sk_live_abc123..." \
6  -H "Content-Type: application/json" \
7  -d '{"data": "'$(base64 -i xrechnung.xml)'", "filename": "xrechnung.xml"}' \
8  | jq '.invoice')
9 
10# 2) Generate the target format from the unchanged invoice JSON
11jq -n --argjson inv "$INVOICE" '{invoice: $inv, formatOptions: {profile: "EN16931"}}' \
12  | curl -s -X POST https://service.invoice-api.xhub.io/api/v1/invoice/de/zugferd/generate \
13      -H "Authorization: Bearer sk_live_abc123..." \
14      -H "Content-Type: application/json" \
15      -d @- \
16  | jq -r '.data' | base64 -d > rechnung-zugferd.pdf

Limits: input invoices from 28 countries are recognized; output covers 11 formats across 14 countries. Conversion goes through the canonical invoice model – format-specific extra fields it does not cover are lost; the parse response flags them in warnings.