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 — 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.

Input

{
    "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:

{
    "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: 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 — start runs, fetch datasets, and manage schedules over REST.
• apify-client for JavaScript and apify-client for Python — official SDKs.
• 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 — trigger downstream actions (CRM import, Slack alert, price-change email) the moment a run finishes.

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 — multi-step automation scenarios.
• Zapier — push new venue leads straight into your CRM.
• Slack — get notified when a monitored city gets a new venue or a price change.
• Google Drive / Sheets — auto-export every run to a spreadsheet.
• Airbyte — pipe results into your data warehouse.
• 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 — 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 pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402 — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server — no account, no API key.
• 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 — UK restaurants, menus, prices & deals.
• Uber Eats Scraper — US & global restaurants, menus & phone leads.
• Foodpanda Scraper — APAC restaurants, menus & leads.
• Zomato Scraper — India & UAE restaurants, menus, ratings & phone leads.
• Fresha Scraper — salon, spa & beauty business leads.
• Booksy Scraper — beauty & wellness provider leads.
• Google Play Store Scraper — apps, reviews & developer leads.
• 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 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. Only new and changed venues are emitted; add a webhook 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. Feature requests are welcome — this actor is actively maintained.