The response from the Get Order endpoint has been enhanced to include a meal cards object, enabling Integrators to determine whether an order was processed using a meal card. Additionally, the payload of the Order Events Webhook Callback now provides meal cards information. This crucial update is also exemplified in the fulfillment types payload example, in Guides section.

The prep-stages endpoint has been updated so that API Integrated partners can now tell Deliveroo if an order is ready or more time is needed to prepare the food. For more detailed information see the API docs.

Customers first name and the ability to contact them through a bridge code is now available in the Order Events Webhook Callback for Deliveroo fulfilled and pick up orders orders. Customer order frequency is also available on all fulfilment types on the Order Events Webhook Callback

The Rider Events Webhook Callback has been updated to use Deliveroo Rider in the full_name field to support rider anonymisation.