Integration · Deliveroo
Deliveroo integration for restaurant groups
Take Deliveroo orders straight into your POS, keep menus and site hours in sync, or book Deliveroo riders for orders from your own app. Here is how each API works and where it stops.
Takes two minutes. An engineer reads it, and Max replies within 1 business day.
- API
- Order, Menu, Site, Express
- Access
- Developer Portal, OAuth
- Docs
- v2.0, updated March 2026
- Markets
- UK, IE, FR, BE, IT, UAE, Kuwait
In short
A Deliveroo integration connects Deliveroo to your POS and kitchen through its Partner Platform Suite: the Order API sends orders by webhook for you to accept, the Menu API takes your full menu, and the Site API controls hours and busy mode. The Express API books Deliveroo riders for your own orders. Access runs through Deliveroo's Developer Portal with OAuth credentials. Orders not accepted within 10 minutes are rejected automatically. dev.family builds Deliveroo connectors and runs them under an SLA.
What data moves
What a Deliveroo integration moves
Read means we can get it from Deliveroo. Write means we can send it to Deliveroo.
| Object | Read | Write | What the API supports |
|---|---|---|---|
| Orders | Yes | Yes | New-order and status webhooks; accept, reject and sync status, preparation stages |
| Menus | Partly | Yes | Full menu upload, processed in the background with a result webhook |
| Item availability | No | Yes | Available, unavailable or hidden per item |
| Sites | Yes | Yes | Open and close, opening hours, days off, busy and quiet mode |
| Express deliveries | Yes | Yes | Quote, schedule, track and cancel riders for your own orders; serviceability check |
| Sales and payouts | No | No | Not in the Partner Platform Suite we checked |
Common setups
How groups connect Deliveroo
Deliveroo into the EPOS
Orders land in the EPOS and on the kitchen screen without a tablet.
Through middleware
One feed for every delivery app, menus pushed from one place.
Riders for your own orders
Your appDeliveroo ExpressCustomerYour channel and your guest data, Deliveroo's riders.
API access
How Deliveroo API access works
Deliveroo gives access through its Developer Portal. You create an application and get OAuth client credentials, with separate sandbox and production hosts; tokens are short-lived. A test-order endpoint generates webhooks without real riders.
If your Deliveroo contract doesn't reference the Partner Platform Suite, your account manager adds it. Technology partners sign up through a separate guide that Deliveroo doesn't publish openly.
Docs api-docs.deliveroo.com, v2.0 (v1.0 legacy) · checked November 9, 2026
What we need from you
- Your Deliveroo restaurant account and sites
- Confirmation that your contract covers the API
- Which brands and menus to connect
- A test site
Getting access:
credentials from the Developer Portal; contract changes go through your account manager.
Platform limits
Where Deliveroo integrations break
Ten minutes to accept. Orders not accepted within 10 minutes are rejected automatically, though this may vary by region. A connector outage turns into lost orders fast.
Menus process in the background. A menu upload returns before it's processed; the result comes by webhook. Your system has to wait for it and handle a rejected menu.
Legacy versions. v2.0 is current, v1.0 is legacy and the old POS webhooks are deprecated. Older integrations need a migration.
Rate limits per endpoint. Limits are listed per endpoint in the API specs, with no global number, and we found no published webhook retry policy.
Ownership change. DoorDash completed its acquisition of Deliveroo in October 2025 and is exiting some markets. Watch for changes to coverage and contracts.
Run
Who fixes it when the platform changes its API
Monitoring
We check the connector against the live API every day and log every failed call.
Versions
We track the platform's changelog and move the connector to a new version before the old one is retired.
Alerts
Lost or stuck orders page the on-call engineer, who fixes them under the SLA.
Questions
Didn't find your answer? Ask on the call.
Yes. Deliveroo's Partner Platform Suite has an Order API, a Menu API and a Site API, documented on its developer portal. The Deliveroo Express API lets a restaurant book Deliveroo riders for orders from its own channels.
Create an application in the Deliveroo Developer Portal to get OAuth client credentials for sandbox and production. Restaurants whose Deliveroo contract doesn't cover the Partner Platform Suite go through their account manager. Deliveroo doesn't publish its technology partner approval steps.
Orders arrive by webhook and you accept, reject and update their status. The full menu is uploaded and processed in the background, with items available, unavailable or hidden. Sites can open, close, change hours and switch to busy mode.
Deliveroo publishes no timeline, and we found no sourced market estimate. The order flow, menu size and number of sites decide the scope; we fix the price before the build.
Many UK EPOS and POS systems take Deliveroo orders through their own integrations or through middleware such as Deliverect. A custom connector makes sense when you need one menu across brands or data the standard route doesn't carry.
Deliveroo lists the UK, Ireland, France, Belgium, Italy, the UAE and Kuwait. DoorDash completed its acquisition of Deliveroo in October 2025.
Get a scope estimate for your Deliveroo integration
Tell us your sites, brands and the POS or EPOS behind them. An engineer will reply with what's possible and how long it takes.
a call with an engineer, then a fixed-price Integration Build. If the connector is part of a bigger change across brands, we start with a 2–3 week Assessment. How we work
Software vendor?We build connectors for food-tech products too, under your brand or ours. Restaurant API for software vendors
Max will reply within 1 business day with what's possible, what access we need and a rough timeline.