Webhook endpoint needs to be configured before this flow is used.
-
Authorize and login (request access token)
-
Create multiple documents (single create document calls, since you need to pair our id with your document)
-
Store Id/Ids from response
-
Wait until webhook payload is delivered to configured endpoint
-
Update your local data according to received events
Webhook document payloads include peppol_original and the Peppol seller item ID in items[].code, as described in Fetch Document. Download URLs expire after 1 hour; if a URL has expired when you process an event, fetch the document again to obtain a fresh URL.
You should have backup polling process (Backup Guide) in place for cases where your endpoint is down for some reason to sync your data. You can even poll every couple of hours to check if there are no left-overs. This is not mandatory if your endpoint has solid uptime.
Our webhook handler will try to deliver the payload 10 times with prolonged delays between attempts. The latest delivery attempt happens approximately 7 hours after first attempt.
You can choose to be notified about webhook delivery failure by filling in the notification_email field. To avoid spam-like email “bursts” only the first occurrence in 24-hour window is notified via email for each webhook endpoint.
Webhooks which failed are also marked with special state “failing”, state_description field contains failure reason (if available). First successful delivery will switch the webhook back to “enabled” state.