List the status events of one received invoice
- In the sandbox
GET
Since 0.35.0. The same events the webhook delivers, in sequence order, each with direction in.
apiKeyheader
AuthorizationBearer <token>Send your key as a bearer token: Authorization: Bearer <your-api-key>. Health is the only call that needs no key.
id*stringThe service's id for a received invoice (returned by POST /received).
Match
^rcv_[0-9a-f]{24}$Events in sequence order.
application/json- response
data*array<>curl -X GET "https://example.com/received/string/events" \ -H "Authorization: Bearer <your-api-key>"{ "data": [ { "event_id": "stringst", "sequence": 1, "occurred_at": "2019-08-24T14:15:22Z", "invoice_ref": "string", "invoice_number": "string", "country_route": "PEPPOL", "environment": "sandbox", "direction": "out", "legal_id": "string", "document_sha256": "string", "buyer_status": "acknowledged", "errors": [ { "code": "string", "source": "string", "message": "string", "field": "string", "fix_hint": "string" } ], "route": { "submission_id": "string", "raw": null }, "status": "buyer_status" } ]}Download a received file or its check GET
Since 0.35.0. The ETag is the SHA-256 of the file.
List and search received invoices GET
Since 0.35.0. The same parameters and answer as GET /invoices, for received invoices only; state is received, validated or validation_failed. A client key sees its own client's; the operator every client's, or one client's with client.