# Wolt Restaurant & Venue Scraper (`crawlerbros/wolt-scraper`) Actor

Scrape restaurants, cafes, grocery stores and other venues from Wolt food delivery platform across 27+ countries including Finland, Sweden, Denmark, Germany, Poland, Japan, Israel and more.

- **URL**: https://apify.com/crawlerbros/wolt-scraper.md
- **Developed by:** [Crawler Bros](https://apify.com/crawlerbros) (community)
- **Categories:** Automation, E-commerce, Developer tools
- **Stats:** 6 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $3.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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 Restaurant & Venue Scraper

Scrape restaurant and venue data from [Wolt](https://wolt.com/) — a leading food delivery platform operating across Europe and the Middle East. Extract restaurant names, cuisines, ratings, delivery estimates, pricing, locations, and images for any of the 49 supported cities across 22 countries.

### What data you can extract

- **Venue ID, name, and description**
- **Cuisine categories** (Pizza, Sushi, Burger, Grocery, etc.)
- **Rating score and review count**
- **Estimated delivery time** (minutes)
- **Currency and price range** (1=budget to 4=luxury)
- **Online status** (currently accepting orders)
- **Delivery availability**
- **Country and city**
- **Street address**
- **GPS coordinates** (latitude/longitude)
- **URL slug and direct Wolt venue link**
- **Minimum order amount**
- **Tags/badges** (Popular, New, Exclusive, etc.)
- **Cover image and logo**

### Scraping modes

| Mode | Description |
|---|---|
| `byCity` | Scrape all venues in a supported city (up to 2000 results per city) |
| `byUrl` | Scrape specific Wolt venue profile URLs |

### Supported cities (49)

**Finland:** Helsinki, Tampere, Turku, Oulu, Espoo

**Sweden:** Stockholm, Gothenburg, Malmö

**Norway:** Oslo, Bergen, Trondheim

**Denmark:** Copenhagen, Aarhus

**Germany:** Berlin, Hamburg, Munich, Frankfurt, Cologne, Düsseldorf, Stuttgart

**Poland:** Warsaw, Kraków, Wrocław, Gdańsk, Poznań, Łódź

**Austria:** Vienna, Graz

**Czechia:** Prague, Brno

**Hungary:** Budapest

**Slovakia:** Bratislava

**Slovenia:** Ljubljana

**Croatia:** Zagreb, Split

**Serbia:** Belgrade

**Estonia:** Tallinn

**Latvia:** Riga

**Lithuania:** Vilnius, Kaunas

**Iceland:** Reykjavik

**Greece:** Athens, Thessaloniki

**Cyprus:** Nicosia, Limassol

**Israel:** Tel Aviv, Jerusalem, Haifa

**Georgia:** Tbilisi

**Azerbaijan:** Baku

### Input configuration

| Field | Type | Description |
|---|---|---|
| `mode` | Select | Scraping mode (`byCity` / `byUrl`) |
| `city` | Select | Target city (for `byCity` mode) |
| `venueUrls` | List | Direct Wolt venue URLs (for `byUrl` mode) |
| `categoryFilter` | Text | Filter by cuisine/category keyword (e.g. `pizza`, `sushi`) |
| `onlineOnly` | Boolean | Only return venues currently accepting orders |
| `maxItems` | Number | Maximum number of results (1–2000, default 100) |
| `proxyConfiguration` | Proxy | Apify proxy settings — Residential proxy is required for reliable results |

### Example input

```json
{
  "mode": "byCity",
  "city": "athens",
  "categoryFilter": "pizza",
  "onlineOnly": true,
  "maxItems": 100,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

### Example output

```json
{
  "venueId": "5e25d0d6cafebabe4afb2a01",
  "name": "Pizza Palace",
  "shortDescription": "Best pizza in Helsinki",
  "categories": ["Pizza", "Italian", "Pasta"],
  "rating": 8.7,
  "ratingCount": 1523,
  "estimateMinutes": 35,
  "currency": "EUR",
  "priceRange": 2,
  "online": true,
  "delivers": true,
  "country": "fin",
  "city": "helsinki",
  "address": "Mannerheimintie 5, Helsinki",
  "latitude": 60.1699,
  "longitude": 24.9384,
  "slug": "pizza-palace-helsinki",
  "tags": ["Popular"],
  "imageUrl": "https://imageproxy.wolt.com/venue/5e25d0d6/cover.jpg",
  "profileImageUrl": "https://imageproxy.wolt.com/venue/5e25d0d6/logo.jpg",
  "venueUrl": "https://wolt.com/en/fin/helsinki/restaurant/pizza-palace-helsinki",
  "recordType": "venue",
  "sourceUrl": "https://consumer-api.wolt.com/v1/pages/restaurants?lat=60.1699&lon=24.9384&slug=helsinki",
  "scrapedAt": "2026-06-01T12:00:00+00:00"
}
```

### Use cases

- **Food delivery market research** — analyze restaurant density, cuisine types, and ratings by city
- **Competitor analysis** — track competing restaurants' ratings, pricing, and delivery performance
- **Location intelligence** — discover which cuisines are most popular in each city
- **Brand monitoring** — track your restaurant's rating and position on Wolt
- **Market entry research** — identify cuisine gaps and opportunities in target cities
- **Price benchmarking** — compare price ranges across cuisine types and cities

### FAQ

**Does it require login or API keys?**
No. Wolt's venue data is publicly accessible without authentication. However, a residential proxy (Apify Residential) is required for reliable access — Wolt blocks standard datacenter IPs.

**How many venues can I get per city?**
Up to 2000 venues per city depending on city size. Athens and Berlin return 2000+ venues; Helsinki returns ~1100.

**How do I filter by cuisine type?**
Use the `categoryFilter` input — it matches any keyword in the venue's category tags (e.g. `pizza`, `sushi`, `burger`, `grocery`, `coffee`).

**Can I check which restaurants are currently open?**
Yes — set `onlineOnly: true` to only return venues currently accepting orders.

**What is the price range scale?**
1 = budget-friendly, 2 = moderate, 3 = premium, 4 = luxury.

**Which cities are supported?**
49 cities across 22 countries are supported — see the full list above. All major Wolt markets in Europe and the Middle East are covered.

**Can I track a specific restaurant's rating over time?**
Yes — run the scraper daily and filter by venue name or slug to track rating changes over time.

**Why do I need a residential proxy?**
Wolt's API blocks requests from datacenter IP ranges. Residential proxies route your requests through real user IPs, ensuring reliable data access. The Apify Residential proxy group is pre-configured as the default.

# Actor input Schema

## `mode` (type: `string`):

byCity: scrape all venues in a city. byUrl: scrape specific Wolt venue profile URLs.

## `city` (type: `string`):

City to scrape venues from. Used in byCity mode.

## `venueUrls` (type: `array`):

List of Wolt venue profile URLs to scrape directly (e.g. https://wolt.com/en/fin/helsinki/restaurant/my-restaurant).

## `categoryFilter` (type: `string`):

Only include venues whose category matches this keyword (e.g. 'pizza', 'sushi', 'grocery'). Case-insensitive.

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

Only return venues that are currently accepting orders.

## `maxItems` (type: `integer`):

Maximum number of venues to return (1–2000).

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

Apify proxy settings. Wolt's API blocks bare datacenter IPs — residential proxies are required for reliable results. Default uses Apify Residential proxy group.

## Actor input object example

```json
{
  "mode": "byCity",
  "city": "helsinki",
  "onlineOnly": false,
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `venues` (type: `string`):

Dataset containing all scraped venue records.

# 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 = {
    "mode": "byCity",
    "city": "helsinki",
    "onlineOnly": false,
    "maxItems": 50,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("crawlerbros/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 = {
    "mode": "byCity",
    "city": "helsinki",
    "onlineOnly": False,
    "maxItems": 50,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("crawlerbros/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 '{
  "mode": "byCity",
  "city": "helsinki",
  "onlineOnly": false,
  "maxItems": 50,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call crawlerbros/wolt-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,crawlerbros/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/srOUAdkD90syqYmhz/builds/kcF2nyQfg1LaI9ghd/openapi.json