Webhook url
- Bauke Rietveld
- Constantijn Molengraaf (Unlicensed)
Deze pagina’s zijn in het engels ten behoeve van mogelijk internationale ontwikkelaars
A webhook url MAY be implemented by the following roles:
Data SERVICE Consumer Data SERVICE BROKER
In order for a data service consumer to subscribe to an event as defined by a data service provider, they must be able to receive notifications containing events via a webhook url. Notifications are only sent for subscriptions with status equal to active (see Lifecycle of a Subscription for more information). Notifications and events are always structured according to the notification, and event objects.
Parties MUST have a webhook url before obtaining a subscription
If a party has a subscription, they MUST support a notification object
The webhook allows data service consumers to receive and act upon notifications from a data service provider. The webhook should follow the generic technical requirements, as well as the requirements specified for specific methods. Further, data service consumers are responsible for determining a suitable authorisation policy for their notifications. See Autorisatie for more information.
The figure below gives an overview of the HTTP methods that are supported by the webhook url. These methods are further detailed and specified in the pages below: