Skip to main content

Ebox Event Service integration

Integration tips​

We strongly recommend an asynchronous implementation with retry so that the DP is not directly impacted by errors of the EES. Event are important so we cannot simply ignore them because they cannot be send.

Example input​

  • EES V1.0.0
[
    {
      "eventType": "newDocument",
      "eventCorrelationId": "c1493fcf-601b-453d-80b8-9db1b226199f",
      "eboxId": "0206731645",
      "messageId": "3b06011b-071d-4e9c-b879-b260523247cb",
      "receiptDate": "2023-04-29T10:25:53.723Z",
      "expirationDate": "2025-04-29T10:25:53.723Z",
      "registeredMail": false
    }
]
  • EES V2.0.0
[
  {
    "eventType": "newDocument",
    "eventCorrelationId": "c1493fcf-601b-453d-80b8-9db1b226199f",
    "enterpriseId": "0206731645",
    "messageId": "3b06011b-071d-4e9c-b879-b260523247cb",
    "receiptDate": "2023-04-29T10:25:53+02:00",
    "expirationDate": "2025-04-29T10:25:53+02:00",
    "registeredMail": false
  }
]

Technical Information​

  • EES Open Api 2 Spec
  • EES v1.1.1
    • Endpoint ACC : https://public.int.fedservices.be/EventServices/Ebox/enterprise/document/events
    • Endpoint PRD : https://public.fedservices.be/EventServices/Ebox/enterprise/document/events
  • EES v2.0.0
    • Endpoint ACC : https://public.int.fedservices.be/EventServices/Ebox/v2/enterprise/document/events
    • Endpoint PRD : https://public.fedservices.be/EventServices/Ebox/v2/enterprise/document/events