Delivery marketplace menu and fee monitoring
Woltエンドポイントを使えば、「Delivery marketplace menu and fee monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn Wolt's public delivery marketplace into structured JSON — a live directory of every city Wolt operates in with the coordinate pair the rest of the family takes, coordinate venue search with keyword, category, sort and store-type filters, the live category catalog behind those filters, Wolt's own curated homepage collections, venue detail and menus, in-venue item search, and live availability with delivery and pickup estimates, fee, order minimum and current discount campaigns. Credential-free.
List every Wolt city with its coordinates, search venues by location, and get menus plus live delivery fees and estimates as JSON.
エンドポイントファミリー
4
ドキュメント化されたパラメータ
31
サンプル数
8
ライブカタログスナップショット
稼働エンドポイント
8
メソッド
GET
必須パラメータ
19
スキーマ参照
8
{
"platform": "Wolt",
"endpoint": "wolt-search",
"method": "GET",
"path": "/wolt/search",
"auth": "apiKey"
}ユースケース
List every Wolt city with its coordinates, search venues by location, and get menus plus live delivery fees and estimates as JSON.
Woltエンドポイントを使えば、「Delivery marketplace menu and fee monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Woltエンドポイントを使えば、「European q-commerce coverage research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Woltエンドポイントを使えば、「Restaurant and dark-store assortment analysis」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のWoltエンドポイントカタログから取得しています（エンドポイント8件、ドキュメント化されたリクエストパラメータ31個、公開レスポンススキーマ8件）。DocsとPlaygroundが参照しているカタログと同じものです。
Woltのエンドポイントは8件、4つのリクエストファミリーに分類されています（Restaurant、Search、Citiesほか1件）。
これらのWoltエンドポイントには31個のリクエストパラメータがドキュメント化されており、うち19個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
8件のWoltエンドポイントのうち8件が実際のサンプルレスポンスを、8件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Woltのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Woltのエンドポイントは8個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/wolt/restaurant
/wolt/search
/wolt/cities
/wolt/collections
エンドポイントカタログ
/wolt/searchReturns restaurants and stores near a coordinate, optionally filtered by a keyword or browsed by category. With none of those, this reads Wolt's own plain location browse; with a query it uses Wolt's own keyword search across restaurant/store names, dishes, and cuisines; with a category it browses Wolt's own per-category listing (the same page a homepage cuisine tile links to) -- call /wolt/search/filters for the current, complete, location-scoped list of valid category values. category and query cannot be combined. A keyword search additionally accepts sort, product_line, and open_now; those three apply to keyword search only and return a 400 without query. Each result carries its slug (the value the restaurant and menu endpoints take), name, address, coordinates, tags, price range, rating, and delivery estimate; the two browse modes additionally carry each venue's own category ids. The response also carries is_serviceable, which says whether Wolt delivers to the requested coordinates at all: false means the coordinates are outside Wolt's delivery coverage, so the empty results list is a coverage answer rather than a no-matches answer. A keyword that simply matches nothing inside a covered area returns an empty list with is_serviceable true. Call /wolt/cities for the coordinates of every city Wolt operates in.
MCPツール wolt_search
/wolt/citiesReturns Wolt's own live directory of every city it operates in, each with the coordinate pair the rest of the Wolt endpoints take, plus its slug, country codes, and timezone. Every other Wolt endpoint is resolved purely from a coordinate, so this is the discovery step that makes them usable without an external geocoder. Optionally restrict to one country, or pass a reference coordinate to have each city carry its distance and the list returned nearest-first.
MCPツール wolt_cities
/wolt/search/filtersReturns the current, location-scoped catalog of every value /wolt/search's category parameter accepts, each with a live restaurant count when Wolt's own homepage currently features that category as one of its curated tiles -- the same data Wolt's own search page's cuisine tiles are populated from.
MCPツール wolt_search_filters
/wolt/collectionsReturns Wolt's own curated homepage restaurant/store lists for a location (e.g. top-rated, newest, hot-this-week -- whichever collections Wolt's own ops team currently curates for that market), read from Wolt's anonymous homepage endpoint. Each restaurant carries the same fields /wolt/search returns. The response also carries is_serviceable, which says whether Wolt delivers to the requested coordinates at all: false means the coordinates are outside Wolt's delivery coverage, so the empty collections list is a coverage answer rather than a served location whose homepage happens to carry no curated lists.
MCPツール wolt_collections
/wolt/restaurantReturns one Wolt restaurant or store's public detail by its slug: name, address, coordinates, timezone, phone, website, rating, currency, price range, cuisine tags, category ids (the values /wolt/search's category parameter accepts), opening hours, delivery hours, delivery methods, pickup availability, order minimum, and service fee estimate.
MCPツール wolt_restaurant
/wolt/restaurant/menuReturns one restaurant/store's menu grouped into categories, plus its restaurant summary. Each item carries a name, description, price, dietary tags, and image, read from Wolt's own anonymous menu API in a single call. The response's loading_strategy field reports whether the items are included: full means every category carries its items, while partial means Wolt does not bulk-load this venue's assortment, so the categories come back real but with empty item lists and the venue's items are reachable only by keyword through /wolt/restaurant/menu/search. Large stores of any type -- supermarkets, pharmacies, drugstores, DIY and toy stores -- are commonly partial; restaurants are full.
MCPツール wolt_restaurant_menu
/wolt/restaurant/menu/searchSearches one restaurant's or store's own items by keyword, using Wolt's own in-venue item search. This is the only way to reach the items of a large grocery or retail store: /wolt/restaurant/menu returns those venues' categories with no items, because Wolt itself only loads such an assortment a slice at a time. Matching works across languages, so an English keyword finds locally-named products. Each item carries a name, description, price, dietary tags, image, and -- for packaged retail products -- a barcode, pack size, and per-unit comparison price. A keyword is required; a no-match keyword returns an empty item list rather than an error.
MCPツール wolt_restaurant_menu_search
/wolt/restaurant/availabilityReturns one restaurant/store's live availability for a delivery coordinate: whether it is open and online right now, the next open and close times, delivery and pickup time estimates in minutes, the delivery fee, the order minimum, the venue's distance, and any discount campaign labels Wolt currently shows on its public page. Coordinates are optional but change the answer materially -- Wolt resolves delivery availability, the fee, the estimate, and the distance against them; without coordinates the venue's generic, location-independent status is returned and delivery_method_default is UNAVAILABLE.
MCPツール wolt_restaurant_availability
関連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.
Woltのスクレイピング方法
Crawlora's Wolt endpoints return normalized public Wolt data as JSON with one API key — no Wolt account required. Every venue-facing call resolves its market from a latitude/longitude pair rather than a city name, which makes the city directory the discovery step that removes the need for an external geocoder.
The cities endpoint returns Wolt's own live directory of every city it operates in, each with the coordinate pair the rest of the family takes, plus its slug, country codes, and timezone. Because search, collections, filters and availability all resolve their market from coordinates alone, this is what makes the whole family usable without an external geocoding service.
The search endpoint takes a latitude and longitude and returns nearby restaurants and stores, optionally narrowed by a keyword, or browsed by a Wolt category id instead — supplying both returns a 400. Sorting, the store-type filter and open-now apply to keyword search only, an upstream limitation rather than a choice here: Wolt exposes those controls on its search surface but not on its plain browse. Each result's slug is what the venue endpoints take.
The search-filters endpoint returns the current, location-scoped catalog of every value the search category parameter accepts, each with a live venue count when Wolt currently features that category as a curated tile — the same data behind its own cuisine tiles. The collections endpoint returns Wolt's curated homepage lists for a location, whichever its ops team is running there: top-rated, newest, hot this week, quickest delivery.
The restaurant endpoint returns one venue's static detail by slug — address, phone, weekly opening hours, rating. The restaurant-menu endpoint returns its menu grouped into categories alongside the venue summary, and the menu-search endpoint searches that one venue's items by keyword using Wolt's own in-venue search rather than filtering client-side.
The availability endpoint is the live counterpart to static venue detail: for a delivery coordinate it returns whether the venue is open and online right now, its next open and close times, delivery and pickup estimates in minutes, the delivery fee, the order minimum, the venue's distance, and any discount campaign labels Wolt is currently showing on its own page.
FAQ
Pull the city directory for coordinates, search venues around one of them, then pass a venue slug to the restaurant, menu and in-venue search endpoints, and read live delivery economics from the availability endpoint — all return structured JSON with one API key.
From the cities endpoint. Every venue-facing Wolt call resolves its market from a latitude/longitude pair rather than a city name, and the cities directory returns Wolt's own live list of operating cities with exactly that coordinate pair, plus slug, country codes and timezone — so no external geocoder is needed.
Because Wolt itself only exposes them on its keyword-search surface. Sorting, the store-type filter and open-now are rejected on a plain coordinate browse — that is an upstream limitation carried through faithfully rather than a gap here. Browsing by a category id is the alternative, and supplying both a keyword and a category returns a 400.
Yes — the availability endpoint returns them live for a specific delivery coordinate: whether the venue is open and online, its next open and close times, delivery and pickup estimates in minutes, the delivery fee, the order minimum, the distance, and any discount campaign labels currently shown. Static venue detail carries address, hours and rating instead.
Yes, and the results distinguish them. Each venue carries a product line — restaurant, grocery, alcohol, pharmacy, pet supply, health and beauty, electronics and others — which doubles as a search filter on the keyword path. Which store types a given market actually stocks varies by city, so read the live catalog rather than assuming a fixed set.