API Docs

Get Peppol status logs

Retrieves the Peppol transmission status logs for a purchase invoice. This shows you the complete journey of your document through the Peppol network.

See the right panel for request and response examples.

For field descriptions and how logs relate to meta_info and the status snapshot, see Peppol Transmission Status.

Rate limit

See Rate limiting for response headers (X-RateLimit-*) and retry guidance.

Path parameters

Parameter	Type	Required	Description
`id`	string	Required	The ID of the purchase invoice.

What are Peppol status logs?

When you send a document through the Peppol network, the system tracks every step of its journey. Status logs show you:

When it was sent — Timestamp of when the document left your system
When it was received — Timestamp of when it arrived at the counterpart Access Point
When it was delivered — Timestamp of when it was successfully delivered
Any errors — If something went wrong, you'll see error messages
Acceptance status — Whether the counterpart system accepted or rejected the document

Response

Status code: 200 OK

Returns an array of Peppol status log entries. Each entry includes:

Field	Type	Description
`id`	string	Unique identifier for the log entry.
`sent_message_id`	string or null	Peppol message ID when sent.
`document_uuid`	string	UUID of the document.
`document_type`	string	Document type (e.g. `SELF_BILLED_INVOICE`).
`sender_id`	string or null	Sender identifier.
`receiver_id`	string or null	Receiver identifier.
`doc_type_id`	string or null	Document type identifier.
`process_id`	string or null	Process identifier.
`country_c1`	string or null	Country code.
`document_xml`	string or null	Document XML when applicable.
`message`	string	Human-readable status message.
`timestamp`	number	Unix timestamp (milliseconds).
`event`	string	Event type (e.g. `DOCUMENT_CREATED`, `DOCUMENT_SUBMITTED`, `VALIDATION_SUCCESS`).

See the right panel for complete response examples. Returns an empty array [] when no transmission events have been recorded yet.

Understanding Peppol transmission

How Peppol transmission works

Document creation — You create a purchase invoice through the API
Automatic conversion — The system converts your document to Peppol-compliant XML format (PINT OM Self-Billing specification)
Electronic address lookup — The system looks up the counterpart Peppol electronic address
Submission — The document is submitted to the Peppol Access Point
Network routing — The Peppol network routes the document to the counterpart Access Point
Delivery — The counterpart system receives and processes the document
Status updates — You receive status updates at each step

Requirements for Peppol transmission

Your business profile must be registered with Peppol (have an electronic address)
Your counterpart's business profile must be registered with Peppol
Both parties must be using compatible Peppol Access Points

Benefits

Automatic delivery — No need to email or print documents
Real-time tracking — Know exactly when your document was delivered
Reduced errors — Automated processing reduces manual data entry errors
Faster settlement — Counterparts receive documents instantly
Compliance — Peppol-compliant documents meet Oman e-invoicing requirements

Relationship to other endpoints

[Get Peppol status](./get-peppol-status) — GET /api/purchase-invoices/{id}/peppol-status returns a single current snapshot with C3 and C5 legs.
Retrieve Peppol status log (this page) — GET /api/purchase-invoices/{id}/peppol-status-logs returns a time-ordered list of events.

Error responses

Status	Description
401 Unauthorized	Authentication required or invalid token.
403 Forbidden	User not authorized to access this purchase invoice.
404 Not Found	Document or Peppol status not found.
500 Internal Server Error	An error occurred while processing the request.