Delivery marketplace research
Mit Deliveroo-Endpunkten verwandelst du delivery marketplace research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn Deliveroo's public marketplace feed into structured JSON — restaurant, grocery, and shopping-store search by coordinate, each partner's full priced catalog with resolved customization options, live sort/filter catalogs with per-location result counts, and delivery/pickup scheduling windows. Credential-free.
Search Deliveroo restaurants, groceries, and shopping stores, get full priced catalogs, and pull live scheduling and filter data as structured JSON.
Endpunkt-Familien
3
Dokumentierte Parameter
30
Beispiele
5
Live-Katalog-Snapshot
Aktive Endpunkte
5
Methoden
GET
Pflichtparameter
13
Schema-Referenzen
5
{
"platform": "Deliveroo",
"endpoint": "deliveroo-search",
"method": "GET",
"path": "/deliveroo/search",
"auth": "apiKey"
}Use Cases
Search Deliveroo restaurants, groceries, and shopping stores, get full priced catalogs, and pull live scheduling and filter data as structured JSON.
Mit Deliveroo-Endpunkten verwandelst du delivery marketplace research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Deliveroo-Endpunkten verwandelst du menu and grocery pricing monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Deliveroo-Endpunkten verwandelst du delivery scheduling and availability tracking in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Deliveroo-Endpunktkatalog — 5 Endpunkte, 30 dokumentierte Request-Parameter und 5 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
5 documented Deliveroo endpoints, grouped into 3 request families — Restaurant, Search and Fulfillment Times.
30 request parameters are documented across those Deliveroo endpoints, 13 of them required — the full input contract is public before you write any integration code.
5 of the 5 Deliveroo endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Deliveroo endpoints document their error responses (400, 404 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
5 hosted MCP tools back the Deliveroo endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/deliveroo/restaurant
/deliveroo/search
/deliveroo/fulfillment-times
Endpunktkatalog
/deliveroo/searchReturns the restaurants (or, with collection set, grocery/shopping stores) Deliveroo's own catalog serves for a latitude/longitude in the given market -- the location's entire feed, not a curated subset (confirmed live: up to 2,700+ results for a single coordinate). Each result carries its uname (the value the restaurant and menu endpoints take), name, image, branch_type, and, when available, rating, delivery time, and distance. Optional collection, cuisine, dietary, dish, min_rating, max_delivery_minutes, max_delivery_fee_pounds, has_offer, deliveroos_choice, and sort parameters narrow and order the same feed -- call /deliveroo/search/filters for the current, complete, location-scoped list of every valid cuisine/dietary/dish value with live result counts. A location with no coverage returns an empty list rather than an error.
MCP-Tool deliveroo_search
/deliveroo/search/filtersReturns the exact same sort and filter catalog -- every cuisine, dietary tag, dish, delivery-time tier, delivery-fee tier, star-rating tier, and offer flag, each with a live result count for this location -- that the real search page's own filter dropdowns are populated from. Every option's query_param/query_value pair is the literal query string /deliveroo/search accepts for that filter.
MCP-Tool deliveroo_search_filters
/deliveroo/restaurantReturns one Deliveroo partner's detail by uname -- restaurant, grocery, or shopping store alike, distinguished by branch_type: name, address, currency, branch/fulfillment type, rating, review count, a hero image, and whether it currently accepts orders.
MCP-Tool deliveroo_restaurant
/deliveroo/restaurant/menuReturns one partner's full menu or catalog grouped into categories -- restaurant menus, grocery aisles, and shopping-store catalogs all use this same endpoint (see /deliveroo/search's collection parameter). Every item carries a name, description, product-meta text when the upstream provides it (calorie counts on restaurant items, per-unit pricing like "380g · £15.79/kg" on grocery/shopping items), price, availability, and its resolved customization options (e.g. "Choose your meal", "Add ingredients?") with each option's own price and required/multi-select bounds.
MCP-Tool deliveroo_restaurant_menu
/deliveroo/fulfillment-timesReturns the exact same "Choose a day" / "Choose a time" scheduled-ordering data the real site's own order-ahead picker shows for a location, for both delivery and pickup: an ASAP option plus every day currently open for a scheduled order, each with its real time slots and UNIX timestamps.
MCP-Tool deliveroo_fulfillment_times
Verwandte APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
So scrapst du Deliveroo
Crawlora's Deliveroo endpoints return normalized public Deliveroo marketplace data as JSON with one API key — no Deliveroo account required. The same endpoints cover restaurants, groceries, and shopping stores alike, distinguished by branch_type.
Pass a latitude and longitude to /deliveroo/search for the curated feed of restaurants (or, with collection set, grocery/shopping stores) Deliveroo's own home page serves — not an exhaustive paginated search. Narrow with cuisine, dietary, dish, min_rating, max_delivery_minutes, max_delivery_fee_pounds, has_offer, and sort.
Call /deliveroo/search/filters for the exact cuisine, dietary, dish, delivery-time, delivery-fee, and rating filter values valid for that location, each with a live result count and the literal query_param/query_value pair /deliveroo/search accepts.
Pass a uname from /deliveroo/search to /deliveroo/restaurant for that partner's profile, or /deliveroo/restaurant/menu for its full menu or grocery/shopping catalog — every item's customization options come resolved with their own price and required/multi-select bounds.
Call /deliveroo/fulfillment-times for the same "Choose a day" / "Choose a time" scheduled-ordering windows the real order-ahead picker shows for a location, for both delivery and pickup.
FAQ
Call /deliveroo/search with a coordinate for the location's feed, /deliveroo/search/filters for valid filter values, /deliveroo/restaurant or /deliveroo/restaurant/menu for one partner's detail and catalog, or /deliveroo/fulfillment-times for scheduling windows — all return structured JSON with one API key.
Yes — /deliveroo/search's collection parameter switches between restaurants, groceries, and shopping stores, and /deliveroo/restaurant/menu returns the same shape for all three: restaurant menus, grocery aisles, and shopping-store catalogs, with per-unit pricing (e.g. "380g · £15.79/kg") on grocery and shopping items.
No — it returns the curated feed of every distinct card Deliveroo's own home page serves for a location, the same discovery experience a user sees on first load, not a full paginated index.
Yes — /deliveroo/fulfillment-times returns the exact ASAP and scheduled-day/time options, with UNIX timestamps, the real site's order-ahead picker currently offers for that location.