List the status events of one invoice
- In the sandbox
In plain words
The same events the webhook delivers, in sequence order. Use it to catch up after downtime.
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}$Events in sequence order.
application/json- response
data*array<>curl -X GET "https://example.com/invoices/inv_bd8bc8b276f38643f1c0f24f/events" \ -H "Authorization: Bearer <your-api-key>"{ "data": [ { "occurred_at": "2026-10-06T19:49:01.621Z", "sequence": 1, "environment": "sandbox", "invoice_ref": "CAPTURE-JSON-1790961440", "document_sha256": "45f857890231e9bc6e73c1ec1e53bc01e7b030f84068b324bdd9ef42b88322bc", "event_id": "evt_e1b58da963c46e4a63409006", "country_route": "DE-XRECHNUNG", "invoice_number": "DOC-mux3dlqm", "status": "received" }, { "occurred_at": "2026-10-06T19:49:02.661Z", "sequence": 2, "environment": "sandbox", "invoice_ref": "CAPTURE-JSON-1790961440", "document_sha256": "45f857890231e9bc6e73c1ec1e53bc01e7b030f84068b324bdd9ef42b88322bc", "event_id": "evt_0dcb4d0b797e93185b22c27d", "country_route": "DE-XRECHNUNG", "invoice_number": "DOC-mux3dlqm", "status": "validated" } ]}Service health GET
Previous
Build and check a document without sending it POST
Runs the schema, the pre-checks, the serializer for the route and every official validation layer, then returns the report and the documents it built, each with its bytes in content_base64 when it is 2 MiB or smaller. Nothing is sent and nothing is stored beyond the request log. Use it while mapping a new client. A number past the limits (see the conventions) answers 422 before any check runs.