Convert UBL XML to ZUGFeRD PDF using REST-API
Upload a UBL 2.1 XML invoice (Peppol BIS Billing 3.0 or plain EN 16931) and receive a ZUGFeRD 2.x compliant PDF/A-3. The API maps the UBL document to CII, renders a clean visual layer, and embeds the CII as factur-x.xml inside a ZUGFeRD-branded PDF/A-3 container.
POST
https://api.invoicexml.com/v1/convert/ubl/to/zugferd
Code Example
curl -X POST https://api.invoicexml.com/v1/convert/ubl/to/zugferd \ -H "Authorization: Bearer YOUR_API_KEY" \ -F "[email protected]"
Request
| Parameter | Type | Description |
|---|---|---|
| file * | binary | The XML invoice file to convert. |
Content-Type: multipart/form-data
Headers
| Header | Value |
|---|---|
| Authorization * | Bearer YOUR_API_KEY |
| Content-Type | multipart/form-data |
Response
200 Converted XML
Returns the ZUGFeRD PDF/A-3 as a binary file.
Content-Type: application/pdf
Frequently Asked Questions
Does the embedded attachment stay UBL?
No. ZUGFeRD 2.x requires CII as the embedded XML. The API maps your UBL document to CII before embedding; the structural conversion preserves every EN 16931 Business Term.
Is the input Schematron-validated?
Yes. The UBL document is validated against EN 16931 rules before the PDF is built. Validation failures are returned as 400 with the specific rule violations.