Configure allergen tagging and modifier structures via the Deliveroo Menu API
domain: api-docs.deliveroo.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Read the Menu API guidelines and overview to understand the required item, category, and modifier schema
For each menu item, populate the allergens array using Deliveroo's defined allergen codes, using the special no_allergens code when an item genuinely has none
Leave the allergens array empty only to signal 'information unavailable' — don't conflate this with no_allergens
Model customer-facing customization (e.g. 'Extra cheese', 'Gluten free bread') as modifiers attached to the relevant item, distinguishing modifiers from separate top-level menu items
Publish the menu update through the Menu API and confirm allergen and modifier data renders correctly on the live Deliveroo listing
Known gotchas
Confusing an empty allergens array (unknown) with the no_allergens code (confirmed none) is a compliance risk — Deliveroo treats them differently for consumer-facing allergy warnings
Menu API access requires Deliveroo partner/API credentials issued through their partner program, not open registration
Allergen and nutrition data can also be edited manually in the Deliveroo Help Centre menu editor — decide whether API-driven or portal-driven allergen management is the source of truth to avoid drift
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?