The Order status notification webhook will be called from Deliveroo when an order is created in Deliveroo. This webhook is triggered on the following events during the order lifecycle:
|The order was created.
|The partner accepted the order.
|The partner rejected the order.
|The partner cancelled the order.
Please notice that while every attempt is made to make callbacks in the order they occurred and in a timely manner, neither can be absolutely guaranteed. It is also possible to receive the same callback more than once.
Check webhook receiver example to get insight into payload sent by Deliveroo.
The Picking API Order status webhook can be configured either at the integrator level, to receive statuses for all partners, or it can be configured at the partner level, to have per-partner webhook URLs. Only one of these options can be used.
Upon registration, your account manager will provide you with a webhook-secret. This secret value will differ from the
api-secret from your credentials. The webhook secret and a sequential globally unique identifier (GUID) are used to generate a Hash-based message authentication code (HMAC) of the order payload.
When you receive a POST webhook request, you will be able to compute a digest and verify that it’s a genuine, authorized request sent from Deliveroo.
A successful webhook callback occurs when the server responds with an HTTP 2xx success range; any other HTTP status or a timeout will result in a retry.
Our servers will retry failed webhook callbacks applying exponential back-off delays and circuit breaking when failures are successive in a short amount of time.
When the circuit breaker is tripped, the total number of requests per minute is significantly reduced until the endpoint appears healthy again.
For order statuses, we "give up" and discard the event callback after 30 minutes.
Updated about 1 year ago