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. Events are important so we cannot simply ignore them because they cannot be sent.

Example input​

  • 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
  }
]

Registered messages​

Document Providers can choose to send messages to the enterprises with the legal value of registered messages based on the modification of the law of february 27th 2019. When using this, it is obligatory that the events that are being sent have the "registeredMail" tag set to true. Based on the "registeredMail" tag the notification system will send separate notifications to the recipients clearly indicating the registered nature of the message.

Registered message notification example​

  • 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": true
  }
]

Technical Information​

  • EES Open Api 2 Spec
  • 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