New
Download the XML of a sent invoice, and of a received invoice
- GET /oauth/invoices/sent/{invoice_id}/xml returns the UBL (PINT-AE) XML the invoice was delivered to Peppol with, exactly as kept when its status became SENT_TO_PEPPOL.
- GET /oauth/invoices/received/{invoice_id}/xml returns the XML a received invoice came in.
- Both answer with the XML as the response body (Content-Type application/xml; charset=utf-8, as a download named Invoice_<number>.xml). Nothing is stored again.
- A sent invoice that has not reached SENT_TO_PEPPOL, or whose send failed, answers 409 invoice_not_sent. The XML of a conversion that was never delivered is never returned.
- The invoice id is checked first: a sent invoice's id is its 24-character invoice_id; a received invoice's id is letters, digits, - and _ (at most 64). Anything else is 400 invalid_invoice_id.
- An invoice of an entity your app cannot reach, or one that does not exist, is 404. A sent or received invoice whose XML is no longer stored is 404 xml_not_available. Errors are { error, code }.
- Files the document carried are links in the XML, not content: download them from the attachments endpoints.
- Any role your app holds on the entity may download. They share the file-download limit of 120 a minute per app; over it, 429 with Retry-After.
Why we changed this
- An integrator needs its own copy of the exact document that was delivered or received, for its records and for audits, without rebuilding it from the invoice data.
What to do: Nothing to change. Call the endpoint when you need the XML; for a sent invoice, wait for SENT_TO_PEPPOL.
Download the XML of a sent invoice →Download the XML of a received invoice →