Download a generated document or the route's receipt
- In the sandbox
In plain words
Kinds: canonical (the JSON as received), erp-export (an ERP export as the ERP sent it), the file as sent (ubl, cii, fa3, pdf), the built document (xrechnung-ubl for Germany, ubl or fa3 otherwise), validation-report and manifest (the SHA-256 of the bytes that go to the route, and the layers that checked them). The four JSON kinds are served as application/json. The ETag is the SHA-256.
apiKeyAuthorizationBearer <token>Send your key as a bearer token: Authorization: Bearer <your-api-key>. Health is the only call that needs no key.
id*stringThe invoice id returned by the submit call.
^inv_[A-Za-z0-9]{16,40}$kind*stringWhich document to fetch.
"ubl""cii""fa3""facturx""pdf""route-receipt""validation-report""manifest""canonical""erp-export"The file. ETag is its SHA-256.
response?stringcurl -X GET "https://example.com/invoices/inv_bd8bc8b276f38643f1c0f24f/documents/ubl" \ -H "Authorization: Bearer <your-api-key>"{}Get an invoice's current state GET
Previous
Invoices received and rejected per day and route GET
Worked out from the store on each call. received counts invoices by the UTC day they arrived; rejected counts invoices now rejected by the UTC day of their last change. A day with nothing has zeros, so a chart has no gaps. Scoped like GET /invoices.