Render PDF

Request body

The request body is the whole document, sent raw (Content-Type: application/xml) — not an object with fields.

Query parameters

How it behaves

• The document can also be sent as a file: multipart/form-data with the fisier field (curl -F fisier=@document.xml), instead of the raw body. The file content becomes the request body, so the result is identical; options stay in the query string, and any other form field next to fisier returns 422 camp_necunoscut.
• Takes the XML of a declaration and returns a readable summary PDF, with the goods, partner, transport, route and documents — the codes translated into names. Local (dompdf), in-memory.
• The document is informative; it does not replace filing in SPV and carries no UIT code (that one is obtained on filing).
• Zero retention: the XML received is not written and not logged.

What it is for

• A printable summary for the driver / transport file.

Response structure

Response examples

The response is a binary document, not JSON: application/pdf, 31,6 KB in this example.

The response is a binary document, not JSON: application/pdf, 31,5 KB in this example.

The response is a binary document, not JSON: application/pdf, 31,6 KB in this example.

Error codes

Errors in the Anaf module use the same envelope as the rest of the platform, with two extra fields: {eroare: {cod, mesaj, camp, request_id}}. eroare.cod is stable and is what you branch on; on validation (422) the code is case-specific: xml_invalid, xml_nu_e_factura, unitate_necunoscuta, luna_invalida and so on. camp points at the offending field when one can be identified.

{
    "eroare": {
        "cod": "xml_invalid",
        "mesaj": "Invalid XML — it cannot be rendered.",
        "camp": null,
        "request_id": "0199c1f0-6e1a-7c3d-9b2f-4a8e5d1c7b04"
    }
}