domain: deliveroo.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register on the Deliveroo self-serve Developer Portal at developers.deliveroo.com and generate an OAuth 2.0 client_id and client_secret
Obtain an access token via the OAuth 2.0 client credentials flow; Deliveroo is migrating from Basic Authentication to OAuth — use OAuth for all new integrations
Call GET /sites/{site_id}/brand to retrieve the brand_id required as a path parameter on all menu endpoints
For standard menu updates, use the Menu API to PATCH specific fields such as prices, images, PLU codes, and item availability
For large menu replacements, use the Menu V3 upload flow: call the endpoint to obtain a presigned S3 URL, PUT the menu JSON directly to S3, then POST to the job creation endpoint to trigger processing; store the returned job_id
Poll the job status endpoint using job_id to confirm successful ingestion or retrieve validation errors
Known gotchas
Deliveroo is deprecating Basic Authentication; integrations still using it must migrate to OAuth before the announced end-of-year cutoff or lose API access
The presigned S3 URL for large menu uploads has a short expiry; upload the menu file immediately after requesting the URL rather than generating it in advance
The Catalogue API is a distinct API intended only for grocery and retail partners managing large item catalogues; do not use it for standard restaurant menu management
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?