XRechnung Rendering API Reference
Upload an XRechnung XML file (CII or UBL syntax) and receive a clean, professionally formatted PDF preview. The API parses the XML, maps every EN 16931 Business Term to a readable layout, and returns a downloadable PDF. The rendered PDF is for human readability only, it carries no legal standing.
https://api.invoicexml.com/v1/render/xrechnung/to/pdf
POST /v1/render/xml/to/pdf,
which accepts any supported invoice XML and detects the syntax itself. Both routes behave identically, so keep this one if the explicit format documents intent, or switch to the generic one to drop the format check from your code.
Code Example
curl -X POST https://api.invoicexml.com/v1/render/xrechnung/to/pdf \ -H "Authorization: Bearer YOUR_API_KEY" \ -F "[email protected]" \ -F "language=en"
Try it out online, no coding required
Upload an XML file and get a readable PDF preview instantly, right in your browser.
Request
| Parameter | Type | Description |
|---|---|---|
| file * | binary | The XML invoice file to render as PDF. |
| language | string | Language for PDF labels and date formatting. Values: en, de, fr. Defaults to en. |
Content-Type: multipart/form-data
Headers
| Header | Value |
|---|---|
| Authorization * | Bearer YOUR_API_KEY |
| Content-Type | multipart/form-data |
Response
200 Rendered PDF
Returns the rendered PDF as a binary file.
Useful resources
Companion material for integrating against the API.
Frequently Asked Questions
Does this work with both UBL and CII XRechnung syntax?
Yes. XRechnung can be encoded in either UBL or CII XML syntax. The API auto-detects the syntax from the root element and renders both correctly.
Is the rendered PDF legally valid?
No. The PDF is a visual representation of the XRechnung data for human readability only. The original XRechnung XML file remains the authoritative invoice document for compliance and tax purposes.
Which XRechnung versions are supported?
Rendering works on any XRechnung version, current 3.0 files as well as older 1.x / 2.x documents, because the preview is built from the EN 16931 Business Terms, which are stable across versions. Rendering is not validation: a retired 2.x file still renders; use POST /v1/validate/xrechnung to check compliance.
Is there one endpoint that takes any invoice XML?
Yes, POST /v1/render/xml/to/pdf. It accepts CII, UBL Invoice, and UBL CreditNote documents and detects the syntax from the root namespace. This XRechnung path is a permanent alias of it, so both routes behave identically and neither is going away. Use the generic one when the incoming format varies, this one when the explicit route documents intent.
Is the invoice data stored?
No. Files are processed entirely in memory and deleted immediately after the PDF is returned. No invoice data is written to disk or retained.
What is the maximum file size?
20 MB. XRechnung files are typically a few kilobytes, so this limit is unlikely to be reached in practice.