# Wolt Scraper - Restaurants, Menus, Prices & Leads (`scrapesage/wolt-scraper`) Actor

Scrape Wolt restaurants & grocery stores by city or coordinates: ratings, cuisines, delivery fees, ETA, price range, address & geo — plus full menus with item prices, modifiers, dietary labels, and merchant legal-entity leads. Monitoring mode for only-new/changed data. No API key, no browser.

- **URL**: https://apify.com/scrapesage/wolt-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Lead generation, Agents, Integrations
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 restaurant / store scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Wolt Scraper — Restaurants, Grocery, Menus, Prices & Merchant Leads

Extract **complete Wolt venue data** across 20+ countries — restaurants *and* grocery/retail stores — with the fields other scrapers skip: **Wolt review scores & counts, real delivery fees, minimum order, service fees, live ETA, full opening & delivery hours, geo, and the merchant's registered legal entity** (business name, business ID, registered address). Optionally pull every venue's **full menu**: items, prices, discounts, dietary labels, images and modifier/option groups with per-choice surcharges.

No login, no cookies, no browser — fast JSON + SSR extraction with 99%+ reliability, straight from Wolt's own public endpoints.

### Why this Wolt scraper?

Most food-delivery scrapers stop at the listing card. This actor pulls Wolt's discovery feed **and** the modern venue detail endpoint **and** the menu, then ships the **richest dataset in the category** — including B2B lead data no other Wolt scraper exposes:

| Data | Typical scrapers | This actor |
|---|---|---|
| Wolt score (0–10) + review count | partial | ✅ |
| Delivery fee, minimum order, service fee, bag fee | ❌ | ✅ |
| Live ETA + full opening **and** delivery hours | ❌ | ✅ |
| Address, post code, lat/lng | partial | ✅ |
| Venue **phone & website** | ❌ | ✅ |
| **Merchant legal entity** (registered name, business ID, address) | ❌ | ✅ |
| Cuisines / tags, price range, Wolt+ status, pickup | partial | ✅ |
| Full **menu** — items, prices, discounts, dietary, images | ❌ | ✅ opt-in |
| Menu **modifiers/options** with per-choice surcharges | ❌ | ✅ opt-in |
| Grocery / retail venues (Wolt Market & partner shops) | ❌ | ✅ |
| Lead score (0–100) per venue | ❌ | ✅ |
| Monitoring — only new / changed venues | ❌ | ✅ |

Wolt operates across the **Nordics, Baltics, DACH, Central, Eastern & Southern Europe, Israel and the Caucasus** — markets that US/UK-focused delivery scrapers don't cover.

### Use cases

- **Restaurant & retail lead generation** — every venue is a business that needs POS, packaging, marketing, insurance, suppliers and delivery tech. Reach them with `phone`, `website` and the registered `merchant` legal entity, and prioritise by `leadScore`, `ratingCount` and `priceRange`.
- **Menu & price intelligence** — track item prices, combo/meal pricing, discounts and modifier surcharges across competitors and cities; benchmark a brand's menu market-by-market.
- **Market research & expansion** — map venue density, cuisine mix, ratings and delivery economics for any Wolt city before entering a market.
- **Delivery & FMCG analytics** — monitor delivery fees, minimum orders, ETAs and Wolt+ adoption over time.
- **Aggregators & apps** — feed restaurant/grocery directories with structured, geocoded venue data.
- **Competitor monitoring** — schedule recurring runs to watch a city for new venues, price changes and rating shifts.

### How to use

1. [Sign up for Apify](https://console.apify.com/sign-up) — the free plan is enough to try this actor.
2. Open the **Wolt Scraper**, enter cities (or coordinates / Wolt URLs), choose whether to include venue detail and menus, and click **Start**.
3. Watch results stream into the dataset table.
4. **Export** as JSON, CSV, Excel, XML, or RSS — or pull results programmatically via the [Apify API](https://docs.apify.com/api/v2).

### Input

```json
{
    "cities": ["Helsinki", "Berlin", "Stockholm"],
    "searchQueries": ["sushi", "pizza"],
    "productLine": "all",
    "maxRestaurants": 200,
    "includeVenueDetail": true,
    "includeMenu": true,
    "includeModifiers": true,
    "minRating": 8,
    "monitorMode": false
}
```

- **cities** — city or address names, geocoded via Wolt (e.g. `Helsinki`, `Berlin`, `Stockholm`, `Copenhagen`, `Tel Aviv`, `Athens`, `Prague`, `Warsaw`, `Budapest`). Each returns every venue that delivers there.
- **coordinates** — precise `lat,lon` points (e.g. `60.1699,24.9384`) to target a neighbourhood instead of a whole city.
- **startUrls** — Wolt venue URLs (`…/restaurant/<slug>`) for single venues, or city URLs to browse.
- **searchQueries** — keep only venues whose name, cuisines or tags match any term (`sushi`, `vegan`, `kebab`, `grocery`, …).
- **productLine** — `all`, `restaurant`, or `grocery` (Wolt Market & partner shops).
- **maxRestaurants** *(default 100)* — cap per location (a big city lists 1,000–2,000).
- **includeVenueDetail** *(default true)* — phone, website, hours, fees, minimum order, payment methods and the merchant legal entity. One light request per venue.
- **includeMenu** *(default false)* — full menu: items, prices, discounts, dietary labels, images and modifiers, grouped by category.
- **includeModifiers** *(default true)* — resolve modifier/option groups (sizes, sides, toppings) with selection rules and surcharge prices.
- **minRating / onlineOnly / openNowOnly / language** — filters and content language.
- **monitorMode** *(default false)* — emit only NEW and CHANGED venues (see below).

### Output

One record per venue (`type: "restaurant"` for restaurants and grocery/retail stores). Menu is nested under `menu` when enabled:

```json
{
    "type": "restaurant",
    "id": "5ae6013cf78b5a000bb64022",
    "slug": "mcdonalds-kamppi-1",
    "name": "McDonald's Helsinki Kamppi",
    "brandName": "McDonald's",
    "productLine": "restaurant",
    "url": "https://wolt.com/en/fin/helsinki/restaurant/mcdonalds-kamppi-1",
    "ratingScore": 8.4,
    "ratingCount": 2561,
    "priceRange": 1,
    "cuisines": ["hamburger", "fries", "salad", "dessert"],
    "currency": "EUR",
    "isOnline": true,
    "isWoltPlus": true,
    "deliveryBasePrice": 1.89,
    "minimumOrder": 10,
    "serviceFee": { "min": 1, "max": 3.99, "percentage": 10 },
    "deliveryEstimateMinutes": 20,
    "deliveryEstimateText": "15-25",
    "address": "Fredrikinkatu 46",
    "city": "Helsinki",
    "postCode": "00100",
    "country": "FIN",
    "latitude": 60.16896,
    "longitude": 24.93015,
    "phone": "+358408330043",
    "website": "http://mcdonalds.fi",
    "openingHours": [{ "day": "Monday", "hours": "06:00–05:59" }],
    "merchant": {
        "name": "Food Folk Suomi Oy",
        "businessId": "2779836-6",
        "streetAddress": "Paciuksenkatu 29, 00270, Helsinki, Finland",
        "country": "Finland"
    },
    "leadScore": 88,
    "menu": {
        "itemCount": 162,
        "categoryCount": 10,
        "minItemPrice": 0.15,
        "maxItemPrice": 20.1,
        "currency": "EUR",
        "categories": [
            {
                "name": "Burgers",
                "items": [
                    {
                        "name": "Big Mac® Meal",
                        "description": "Big Mac®, large fries, large drink.",
                        "price": 14.35,
                        "originalPrice": null,
                        "dietary": [],
                        "vatPercentage": 13,
                        "image": "https://wolt-menu-images-cdn.wolt.com/...",
                        "options": [
                            {
                                "name": "Drink",
                                "required": true,
                                "minSelections": 1,
                                "maxSelections": 1,
                                "choices": [{ "name": "Coca-Cola", "price": 0.35 }]
                            }
                        ]
                    }
                ]
            }
        ]
    },
    "searchLocation": "Helsinki, Finland",
    "scrapedAt": "2026-06-17T01:47:10.471Z"
}
```

### Monitoring mode — only new & changed venues

Turn on **monitorMode** and the actor remembers every venue it has seen (in a named key-value store) and emits only:

- **new** venues that appeared since the last run, and
- **updated** venues whose rating, delivery fee, minimum order, online status, price range, promotions or menu price range changed (tagged with `changeType`).

This is perfect for tracking a city on a schedule without re-paying for unchanged rows. It works **alongside** Apify [Schedules](https://docs.apify.com/platform/schedules): the schedule decides *when* the actor runs, monitor mode decides *what* gets emitted — no conflict. Use a distinct `monitorStoreName` per tracked city or feed to keep histories separate.

### Automate & schedule

Run this actor on autopilot and pull results into your own stack:

- **[Apify API](https://docs.apify.com/api/v2)** — start runs, fetch datasets, and manage schedules over REST.
- **[apify-client for JavaScript](https://docs.apify.com/api/client/js/)** and **[apify-client for Python](https://docs.apify.com/api/client/python/)** — official SDKs.
- **[Schedules](https://docs.apify.com/platform/schedules)** — run it hourly/daily/weekly to monitor new venues, price changes, or rating shifts in a city; combine with `monitorMode` for only-new data.
- **[Webhooks](https://docs.apify.com/platform/integrations/webhooks)** — trigger downstream actions (CRM import, Slack alert, price-change email) the moment a run finishes.

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/wolt-scraper').call({
    cities: ['Helsinki', 'Tallinn'],
    includeMenu: true,
    maxRestaurants: 200,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} Wolt venues & menus`);
```

### Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

- **[Make](https://docs.apify.com/platform/integrations/make)** — multi-step automation scenarios.
- **[Zapier](https://docs.apify.com/platform/integrations/zapier)** — push new venue leads straight into your CRM.
- **[Slack](https://docs.apify.com/platform/integrations/slack)** — get notified when a monitored city gets a new venue or a price change.
- **[Google Drive / Sheets](https://docs.apify.com/platform/integrations/drive)** — auto-export every run to a spreadsheet.
- **[Airbyte](https://docs.apify.com/platform/integrations/airbyte)** — pipe results into your data warehouse.
- **[GitHub](https://docs.apify.com/platform/integrations/github)** — trigger runs from commits or releases.

### Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. You can call this actor from Claude, ChatGPT, or any agent framework through the **[Apify MCP server](https://docs.apify.com/platform/integrations/mcp)** — ask your assistant to "find the top-rated sushi restaurants in Helsinki on Wolt and list their menus and contact details" and let it run this scraper for you.

### Agent-ready: autonomous payments (x402 & Skyfire)

This actor is **agent-ready** — AI agents can discover it, run it, and **pay for it autonomously**, with no Apify account and no human in the loop. It uses [pay-per-event](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) — no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/skyfire)** — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

### More scrapers from scrapesage

Build a complete **food-delivery & local-business intelligence stack** — same rich data, every major platform and region:

- **[Just Eat Scraper](https://apify.com/scrapesage/just-eat-scraper)** — UK restaurants, menus, prices & deals.
- **[Uber Eats Scraper](https://apify.com/scrapesage/ubereats-scraper)** — US & global restaurants, menus & phone leads.
- **[Foodpanda Scraper](https://apify.com/scrapesage/foodpanda-scraper)** — APAC restaurants, menus & leads.
- **[Zomato Scraper](https://apify.com/scrapesage/zomato-scraper)** — India & UAE restaurants, menus, ratings & phone leads.
- **[Fresha Scraper](https://apify.com/scrapesage/fresha-scraper)** — salon, spa & beauty business leads.
- **[Booksy Scraper](https://apify.com/scrapesage/booksy-scraper)** — beauty & wellness provider leads.
- **[Google Play Store Scraper](https://apify.com/scrapesage/google-play-scraper)** — apps, reviews & developer leads.
- **[Website Contact Scraper](https://apify.com/scrapesage/website-contact-scraper)** — turn any venue website into emails, phones & socials.

### Tips

- **Big cities**: a single coordinate returns every venue delivering there (often 1,000–2,000). Use `maxRestaurants` to cap, or several `coordinates` to cover neighbourhoods edge-to-edge.
- **Cheapest, fastest runs**: keep `includeMenu` off for a listing + detail sweep; turn it on only for the venues you actually need menus for (it fetches a larger page per venue).
- **Grocery intelligence**: set `productLine` to `grocery` to target Wolt Market and partner shops.
- **Recurring monitoring**: combine [Schedules](https://docs.apify.com/platform/schedules) with `monitorMode` to capture only new venues and price changes.
- **Proxies**: the default datacenter proxy works well with Wolt; switch to RESIDENTIAL only if you see rate-limiting on very large runs.

### FAQ

**Which countries does Wolt cover?** Wolt operates across the Nordics (Finland, Sweden, Norway, Denmark), the Baltics, Germany, Greece, Cyprus, Malta, the Czech Republic, Slovakia, Hungary, Poland, Croatia, Serbia, Israel, Georgia, Kazakhstan, Azerbaijan and more. Enter any Wolt city in `cities`.

**Do I need a Wolt account or API key?** No. This actor uses Wolt's public web endpoints — no login, no key, no browser.

**Where do the phone, website and merchant details come from?** From Wolt's own public venue detail page — the same information a customer sees, including the legally-required merchant (trader) identity.

**Can I get full menus with prices?** Yes — enable `includeMenu`. You get every item with price, description, discounts, dietary labels, images and modifier/option groups (with per-choice surcharges), grouped by category.

**How do I monitor new venues or price changes automatically?** Enable `monitorMode` and create a [Schedule](https://docs.apify.com/platform/schedules). Only new and changed venues are emitted; add a [webhook](https://docs.apify.com/platform/integrations/webhooks) to push them into your CRM or Slack.

**A field is null — why?** Some venues genuinely don't publish a website, phone or certain fees, and grocery stores have no "cuisines". Fields are `null` only when the data doesn't exist, not because the scraper skipped them.

**Is scraping Wolt legal?** This actor collects publicly available data only. You are responsible for using the data in compliance with applicable laws (GDPR for personal data) and Wolt's terms.

### Need help?

Open an issue on the actor's **Issues** tab, or visit the [Apify help center](https://help.apify.com/). Feature requests are welcome — this actor is actively maintained.

# Actor input Schema

## `cities` (type: `array`):

City (or address) names to scrape. Each is geocoded via Wolt and returns every venue that delivers there — e.g. `Helsinki`, `Berlin`, `Stockholm`, `Copenhagen`, `Tel Aviv`, `Athens`, `Prague`, `Warsaw`, `Budapest`. Wolt operates across the Nordics, Baltics, DACH, Central/Eastern & Southern Europe, Israel and the Caucasus.

## `coordinates` (type: `array`):

Precise delivery points as `lat,lon` strings, e.g. `60.1699,24.9384`. Use this to target a specific neighbourhood instead of a whole city. Returns every venue delivering to that point.

## `startUrls` (type: `array`):

Wolt URLs. A venue URL (`https://wolt.com/en/fin/helsinki/restaurant/<slug>`) scrapes that single venue (with detail and, optionally, its menu). A city URL (`https://wolt.com/en/fin/helsinki`) is resolved to that city's coordinates and browsed.

## `searchQueries` (type: `array`):

Only keep venues whose name, cuisines or tags contain any of these terms, e.g. `sushi`, `pizza`, `burger`, `vegan`, `kebab`, `grocery`, `breakfast`. Leave empty for all venues in the location.

## `productLine` (type: `string`):

Restrict to restaurants or to grocery/retail stores (Wolt Market & partner shops). `All` returns everything.

## `maxRestaurants` (type: `integer`):

Cap on venues collected per city/coordinate (a big city can list 1,000–2,000). The default keeps runs fast and cheap.

## `includeVenueDetail` (type: `boolean`):

For each venue, fetch its detail page for phone, website, full opening & delivery hours, service/bag fees, minimum order, payment methods and the merchant legal entity (registered business name, business ID and address) — ideal for B2B lead generation. One light request per venue. Turn off for a faster, listing-only run (the listing already has rating, cuisines, delivery fee, ETA and geo).

## `includeMenu` (type: `boolean`):

For each venue, also extract its complete menu: every item with description, price, discounts, dietary labels, images and (optionally) modifier/option groups, grouped by category. This is the headline feature for price monitoring and menu analysis. Adds one larger request per venue.

## `includeModifiers` (type: `boolean`):

When menus are included, also resolve item modifier/option groups (e.g. sizes, toppings, sides, choices) with their names, selection rules and surcharge prices.

## `minRating` (type: `integer`):

Only keep venues with a Wolt score at or above this value (Wolt scores run 0–10). 0 = keep all.

## `onlineOnly` (type: `boolean`):

Only keep venues currently online (accepting orders right now).

## `openNowOnly` (type: `boolean`):

Only keep venues that are online and currently delivering.

## `language` (type: `string`):

Two-letter language code for Wolt content (venue descriptions, menu item names), e.g. `en`, `fi`, `sv`, `de`, `da`, `pl`, `cs`, `el`. Defaults to English; falls back to the venue's local language where English is unavailable.

## `monitorMode` (type: `boolean`):

Remember venues seen in previous runs (in a named key-value store) and emit only NEW venues and ones whose rating, delivery fee, minimum order, online status, price range, promotions or menu price range changed (tagged with `changeType`). Perfect for tracking a city on a schedule without re-paying for unchanged rows. Works alongside Apify Schedules — schedule the run, this controls what's emitted.

## `monitorStoreName` (type: `string`):

Named key-value store holding the 'already seen' venue ids/fingerprints for monitoring mode. Use a different name per tracked city/feed to keep histories separate. Lowercase letters, digits and hyphens only.

## `maxConcurrency` (type: `integer`):

Maximum number of venue detail/menu requests fetched in parallel.

## `proxyConfiguration` (type: `object`):

Proxy settings. Apify Proxy is recommended. The default datacenter proxy works well with Wolt; switch to RESIDENTIAL only if you see rate-limiting on very large runs.

## `urlsFromFile` (type: `string`):

Paste a list of URLs (one per line), OR one link to a .txt/.csv file, Google Sheet or Google Drive file containing them. Lets you import many Start URLs at once instead of typing each. Google Sheet/Drive share links are handled automatically.

## Actor input object example

```json
{
  "cities": [
    "Helsinki"
  ],
  "productLine": "all",
  "maxRestaurants": 100,
  "includeVenueDetail": true,
  "includeMenu": false,
  "includeModifiers": true,
  "minRating": 0,
  "onlineOnly": false,
  "openNowOnly": false,
  "language": "en",
  "monitorMode": false,
  "monitorStoreName": "wolt-monitor",
  "maxConcurrency": 6,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All scraped venue records (restaurants and grocery/retail stores), each with optional full menu, as JSON items in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "cities": [
        "Helsinki"
    ],
    "urlsFromFile": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/wolt-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "cities": ["Helsinki"],
    "urlsFromFile": "",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/wolt-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "cities": [
    "Helsinki"
  ],
  "urlsFromFile": ""
}' |
apify call scrapesage/wolt-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/wolt-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/DwvGLccdW2Rn8BlTD/builds/e2yboMvd1ybjRpSgK/openapi.json