Delivery marketplace research
Deliverooエンドポイントを使えば、「Delivery marketplace research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
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.
エンドポイントファミリー
3
ドキュメント化されたパラメータ
29
サンプル数
5
ライブカタログスナップショット
稼働エンドポイント
5
メソッド
GET
必須パラメータ
13
スキーマ参照
5
{
"platform": "Deliveroo",
"endpoint": "deliveroo-search",
"method": "GET",
"path": "/deliveroo/search",
"auth": "apiKey"
}ユースケース
Search Deliveroo restaurants, groceries, and shopping stores, get full priced catalogs, and pull live scheduling and filter data as structured JSON.
Deliverooエンドポイントを使えば、「Delivery marketplace research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Deliverooエンドポイントを使えば、「Menu and grocery pricing monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Deliverooエンドポイントを使えば、「Delivery scheduling and availability tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のDeliverooエンドポイントカタログから取得しています（エンドポイント5件、ドキュメント化されたリクエストパラメータ29個、公開レスポンススキーマ5件）。DocsとPlaygroundが参照しているカタログと同じものです。
Deliverooのエンドポイントは5件、3つのリクエストファミリーに分類されています（Restaurant、Search、Fulfillment Times）。
これらのDeliverooエンドポイントには29個のリクエストパラメータがドキュメント化されており、うち13個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
5件のDeliverooエンドポイントのうち5件が実際のサンプルレスポンスを、5件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Deliverooのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Deliverooのエンドポイントは5個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/deliveroo/restaurant
/deliveroo/search
/deliveroo/fulfillment-times
エンドポイントカタログ
/deliveroo/searchReturns the restaurants (or, with collection set, grocery/shopping stores) Deliveroo's own home feed serves for a latitude/longitude in the given market -- a curated feed of every distinct card the location's page carries, not an exhaustive paginated search. Each result carries its uname (the value the restaurant and menu endpoints take), name, image, and, when the upstream page includes it, rating, delivery time, and distance. Optional collection, cuisine, dietary, dish, min_rating, max_delivery_minutes, max_delivery_fee_pounds, has_offer, 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ツール 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ツール 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ツール 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ツール 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ツール deliveroo_fulfillment_times
関連API
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.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
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.