List the templates
Every template in the catalogue, oldest first, without the `mustache` and `base64` bodies. Pick an id for render. Not counted against your quota.
Your API key as a bearer token: Authorization: Bearer of_live_…. An of_test_ key uses the sandbox — same URL, same templates.
In: header
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/e-invoice/templates"{ "templates": [ { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" } ]}Get a template GET
The full template, as the engine receives it: `mustache` (the XHTML + Mustache source) and `base64` (name → base64 file map — the fonts and images the source references as `base64:<name>`). Not counted against your quota.
Render an invoice with a template → Factur-X PDF POST
The body is the invoice JSON — exactly what `/e-invoice/invoice2XML` accepts, with the line items under `zfitems`. Amounts are passed to the engine digit for digit as you sent them. The engine computes every total from the line items (totals in the body are not used), renders the template to PDF/A-3 and embeds the EN 16931 CII XML as `factur-x.xml`. A line whose VAT amount needs more than two decimals (for example 2.5 × 30.50 at 19 %) is refused by the engine with `422 RENDER_REJECTED` and the message `Rounding necessary`. Counted against your quota like any engine call.