Listening for Rider Events

Once you have configured the Rider Events webhook, Deliveroo will begin notifying your integration about rider-related events using the Rider Events Webhook Callback.

Unlike the Order Events webhook, the Rider Events webhook is meant to be informational. How you process the information provided through this webhook depends on your requirements.

A typical rider status lifecycle is rider_assigned → rider_arrived → rider_confirmed_at_restaurant → rider_in_transit.

Please note that several riders can be assigned to an order if it's too big for one to fulfil. You can expect to see repeated statuses in those cases.

Ride Statuses

Rider Status	Description
rider_assigned	Deliveroo has assigned a rider to the order.
rider_arrived	The rider is nearing the restaurant.
rider_confirmed_at_restaurant	The rider has reached the site, confirmed on the Rider's App.
rider_unassigned	The rider was unassigned from the order.
rider_in_transit	The rider is enroute to the customer.

How do Rider Events Work?

Deliveroo sends you a notification via Rider Events webhook (rider.status_update) every time an event related to the rider and corresponding order occurs:

When a rider is assigned to transport the order, you will receive a rider_assigned event.
You will receive a rider_arrived event when a rider is close to a site.
You will receive a rider_confirmed_at_restaurant when the rider confirms to be at the site on the Rider App.
When a rider is unassigned from the order, you will receive a rider_unassigned event.
You will receive a rider_in_transit when the rider is enroute to the customer.

Failures

Retry Logic

Deliveroo will retry the request for up to 10 minutes.