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

Scrape Talabat across UAE, Saudi, Kuwait, Qatar, Bahrain, Oman, Jordan & Egypt: restaurants, ratings, delivery fees, ETA, geo, full menus with item prices & discounts, customer reviews and merchant B2B leads. Monitoring mode for only-new data. No API key, no browser.

- **URL**: https://apify.com/scrapesage/talabat-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 $2.78 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## Talabat Scraper — Restaurants, Menus, Prices, Reviews & Merchant Leads

Extract **complete Talabat data** across the Middle East & North Africa — **restaurants and stores, full menus with item prices and discounts, customer reviews, and merchant B2B leads** — in one fast, structured run. Covers **UAE, Saudi Arabia, Kuwait, Qatar, Bahrain, Oman, Jordan and Egypt**.

No login, no cookies, no browser — direct JSON/SSR extraction with high reliability and a built-in monitoring mode.

### Why this Talabat scraper?

Talabat (Delivery Hero) is the #1 food-delivery platform in MENA. Most scrapers stop at the restaurant card. This actor is the **richest all-in-one in the category** — restaurant intelligence **plus** full menus, reviews, **and** ready-to-use merchant leads, with only-new monitoring:

| Data | Typical scrapers | This actor |
|---|---|---|
| Restaurant rating, review/rating count | partial | ✅ |
| Delivery fee, minimum order, ETA, status | ❌ | ✅ |
| Cuisines, vertical (restaurant / grocery / pharmacy) | partial | ✅ |
| Geo (lat/lng), area & city | ❌ | ✅ |
| Payment methods, talabat GO flag | ❌ | ✅ |
| **Full menu** — item name (EN + Arabic), description, price | partial | ✅ |
| Old price + **discount %**, highlights, item images | ❌ | ✅ |
| **Customer reviews** (rating, text, reviewer, date) | ❌ | ✅ opt-in |
| **Merchant B2B leads** + 0–100 lead score | ❌ | ✅ opt-in |
| **Monitoring mode** (only new / changed) | ❌ | ✅ |
| 8 MENA markets, EN/AR content | partial | ✅ |

### Use cases

- **Menu & price intelligence** — track item prices, discounts and menu changes across competitors and your own brand on a schedule.
- **Lead generation** — every restaurant is a B2B prospect for food-tech, POS, payments, delivery-SaaS, ghost-kitchen, packaging and ingredient suppliers. Score merchants by popularity (`ratingCount`), quality (`rating`) and activity, and target by city, cuisine or vertical.
- **Market & competitor research** — map who delivers where, at what fees and ETAs, with what ratings, across the Gulf and Egypt.
- **Reputation monitoring** — pull recent customer reviews per restaurant and watch sentiment over time.
- **Catalog & aggregation** — feed apps, dashboards and price-comparison tools with structured restaurant + menu data.

### 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 **Talabat Scraper**, pick a **country**, enter **search queries** (or cities / area slugs / URLs), and click **Start**.
3. Watch restaurants, menus, reviews and leads stream into the dataset table.
4. **Export** as JSON, CSV, Excel, XML, or RSS — or pull results via the [Apify API](https://docs.apify.com/api/v2).

### Input

```json
{
    "country": "uae",
    "searchQueries": ["burger"],
    "cities": ["Dubai"],
    "maxRestaurants": 60,
    "includeMenu": true,
    "includeReviews": false,
    "includeMerchantLeads": true,
    "monitorMode": false
}
```

- **country** — `uae`, `ksa`, `kuwait`, `qatar`, `bahrain`, `oman`, `jordan` or `egypt`.
- **searchQueries** — keywords (`burger`, `pizza`, `sushi`, `shawarma`, `KFC`…) searched across the whole country. No location needed.
- **cities** — city names (`Dubai`, `Riyadh`, `Doha`, `Cairo`…) resolved to Talabat delivery areas; returns every restaurant delivering there (richest data).
- **areaSlugs / areaIds / startUrls** — target precise delivery areas, or paste any Talabat area / restaurant / search URL (auto-routed).
- **restaurantSlugs / branchIds** — scrape specific restaurants or branches directly.
- **includeMenu** *(default true)* — full menu with item prices, discounts, EN/Arabic names and images.
- **includeItemDetails** *(default true)* — keep item descriptions and image URLs.
- **includeReviews** *(default false)* + **maxReviewsPerRestaurant** — customer reviews as separate records.
- **includeMerchantLeads** *(default true)* — one deduplicated merchant lead per restaurant with a 0–100 lead score.
- **minRating / vendorType / language** — filters and content language (`en` / `ar`).
- **monitorMode** *(default false)* — emit only NEW and CHANGED restaurants/reviews (see below).

### Output

One record per restaurant (`type: "restaurant"`), plus optional `type: "review"` and `type: "merchantLead"` records:

```json
{
    "type": "restaurant",
    "branchId": 669895,
    "restaurantId": 643479,
    "name": "Puzatic restaurant, Business Bay",
    "slug": "puzatic-restaurant-business-bay",
    "url": "https://www.talabat.com/uae/puzatic-restaurant-business-bay",
    "country": "United Arab Emirates",
    "city": "Dubai",
    "area": "Business Bay",
    "cuisines": ["Russian", "Uzbek", "Burgers", "Grills", "Sushi"],
    "rating": 4.6,
    "ratingCount": 1000,
    "deliveryFee": 0,
    "minimumOrder": 20,
    "deliveryTimeText": "Within 32 mins",
    "status": "open",
    "isTalabatGO": true,
    "vertical": "restaurant",
    "currency": "AED",
    "latitude": 25.1876,
    "longitude": 55.2843,
    "paymentMethods": ["cash", "credit_card"],
    "menu": {
        "sectionCount": 16,
        "itemCount": 142,
        "minItemPrice": 5,
        "maxItemPrice": 145,
        "currency": "AED",
        "sections": [
            {
                "name": "Picks for you 🔥",
                "items": [
                    {
                        "name": "Chicken Noodle Soup",
                        "nameArabic": "شوربة نودلز بالدجاج",
                        "description": "Classic soup made with chicken, noodles and vegetables.",
                        "price": 45,
                        "currency": "AED",
                        "oldPrice": 50,
                        "discountPercent": 10,
                        "image": "https://images.deliveryhero.io/image/talabat/MenuItems/..."
                    }
                ]
            }
        ]
    },
    "leadScore": 78,
    "scrapedAt": "2026-06-18T06:30:00.000Z"
}
```

### 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, 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 menu prices, new restaurants or reviews in a city or cuisine.
- **[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/talabat-scraper').call({
    country: 'uae',
    cities: ['Dubai'],
    includeMenu: true,
    includeMerchantLeads: true,
    maxRestaurants: 100,
});

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

#### Monitoring mode (only new / changed)

Turn on **monitorMode** to remember everything seen in previous runs (in a named key-value store) and emit only **new** restaurants/reviews and ones whose **rating, delivery fee, minimum order, status or menu price range** changed (tagged with `changeType`). This is independent of, and complements, [Apify Schedules](https://docs.apify.com/platform/schedules): the schedule decides *when* the run fires, monitor mode decides *what* is emitted — so you never pay for unchanged rows.

### 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 merchant leads straight into your CRM.
- **[Slack](https://docs.apify.com/platform/integrations/slack)** — get notified when a monitored city/cuisine changes.
- **[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. 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 burger restaurants in Dubai with their menu prices" 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-commerce intelligence stack** across every region:

- **[Wolt Scraper](https://apify.com/scrapesage/wolt-scraper)** — restaurants, menus & merchant leads across the Nordics, Baltics, DACH & CEE.
- **[Just Eat Scraper](https://apify.com/scrapesage/just-eat-scraper)** — UK restaurants with full menus, prices & deals.
- **[Uber Eats Scraper](https://apify.com/scrapesage/ubereats-scraper)** — US & global restaurants, menus, prices & phone leads.
- **[foodpanda Scraper](https://apify.com/scrapesage/foodpanda-scraper)** — APAC restaurants, menus & geo.
- **[Zomato Scraper](https://apify.com/scrapesage/zomato-scraper)** — India & UAE restaurants, menus, ratings & phone leads.
- **[Property Finder Scraper](https://apify.com/scrapesage/property-finder-scraper)** — UAE/GCC real-estate listings & agent leads.

### Tips

- **Search is the fastest start** — set a `country` and a couple of `searchQueries`; no geo needed. Use `cities`/`areaSlugs` for full delivery-area coverage.
- **Big cities** — one central delivery area can list thousands of restaurants. Raise `maxAreaPages` and `maxRestaurants` to exhaust an area; add more areas with `maxAreasPerCity`.
- **Cost control** — turn `includeMenu` off for listing-only runs (cheaper); reviews and leads are opt-in and deduplicated.
- **Recurring monitoring** — combine [Schedules](https://docs.apify.com/platform/schedules) with `monitorMode` to track only new restaurants, price changes or reviews.
- **Proxies** — the default datacenter proxy works; switch to RESIDENTIAL (country AE/SA/…) only if you hit rate-limiting on very large runs.

### FAQ

**Which countries are supported?** UAE, Saudi Arabia (KSA), Kuwait, Qatar, Bahrain, Oman, Jordan and Egypt — set `country`.

**Do I need a Talabat API key or login?** No. The actor reads the same public pages and JSON endpoints a normal visitor's browser does — no key, no login, no browser automation.

**Can I get full menus with prices?** Yes — keep `includeMenu` on. Each item includes name (English + Arabic), description, price, old price & discount %, highlights and image, grouped by menu section.

**Does it provide merchant contact details?** Talabat (like most food-delivery platforms) doesn't publish a restaurant's phone or email. The merchant lead is the qualified **business profile** — name, city/area, geo, cuisines, rating, popularity, delivery economics, vertical and a lead score — ideal for prospecting and enrichment.

**Can I export to Google Sheets, CSV, or Excel?** Yes — one click in the dataset view, or automatically on every run via the [Google Drive integration](https://docs.apify.com/platform/integrations/drive).

**How do I monitor menu prices or new restaurants automatically?** Turn on `monitorMode` and create a [Schedule](https://docs.apify.com/platform/schedules); optionally add a [webhook](https://docs.apify.com/platform/integrations/webhooks) to push changes into your tools.

**A field is null — why?** Some restaurants genuinely don't publish a value (e.g. no reviews yet, no discount). Fields are `null` only when the data doesn't exist, not because the scraper skipped them.

**Is scraping Talabat legal?** This actor collects publicly available data only. You are responsible for using the data in compliance with applicable laws (e.g. GDPR/CCPA for personal data) and Talabat'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

## `country` (type: `string`):

Talabat market to scrape. Talabat is the Middle East & North Africa food-delivery leader (Delivery Hero). Search, cities and area inputs all apply to this country.

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

Keywords to search Talabat for matching restaurants/cuisines in the selected country, e.g. `burger`, `pizza`, `sushi`, `shawarma`, `breakfast`, `KFC`, `healthy`. No location needed — search covers the whole country. Each match is enriched with full restaurant data (and menu/reviews if enabled).

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

City names to discover restaurants by delivery area, e.g. `Dubai`, `Abu Dhabi`, `Riyadh`, `Jeddah`, `Doha`, `Kuwait City`, `Manama`, `Muscat`, `Amman`, `Cairo`. Each city is resolved to its Talabat delivery area(s); every restaurant delivering there is returned (richest data — ratings + delivery economics + geo). English names work best.

## `areaSlugs` (type: `array`):

Precise Talabat delivery-area slugs in the selected country, e.g. `dubai-marina`, `al-badaa`, `business-bay`, `jumeirah`. Returns every restaurant delivering to that area. Find slugs in any Talabat area URL: talabat.com/uae/restaurants/{areaId}/{slug}.

## `areaIds` (type: `array`):

Numeric Talabat area IDs (the number in talabat.com/{country}/restaurants/{areaId}/{slug}). Use when you already know the exact delivery area.

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

Talabat URLs, auto-routed: an area URL (`/uae/restaurants/1172/al-badaa`) browses that area; a restaurant URL (`/uae/<restaurant-slug>`) scrapes that restaurant; a search URL (`/uae/restaurants?searchTerm=pizza`) runs that search.

## `restaurantSlugs` (type: `array`):

Direct restaurant slugs in the selected country, e.g. `india-palace-restaurant`. Scrapes each restaurant (with menu/reviews if enabled).

## `branchIds` (type: `array`):

Direct Talabat branch IDs. Fetches the menu and reviews for each branch without discovery (fastest, lowest-cost path when you already have IDs).

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

Maximum number of restaurants to collect for this run (across all discovery sources). A single city/area can list thousands; the default keeps runs fast and cheap.

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

For each restaurant, extract its complete menu: every item with name (EN + Arabic), description, price, old price & discount %, highlights and images, grouped by menu section. The headline feature for price monitoring and menu analysis. One extra request per restaurant.

## `includeItemDetails` (type: `boolean`):

When menus are included, also keep each item's description and image URL. Turn off for a leaner price-only menu.

## `includeReviews` (type: `boolean`):

Emit recent customer reviews for each restaurant as separate records (reviewer name, rating, text, date). Great for reputation monitoring.

## `maxReviewsPerRestaurant` (type: `integer`):

Cap on reviews collected per restaurant when reviews are included.

## `includeMerchantLeads` (type: `boolean`):

Also output one deduplicated merchant lead record per restaurant (business name, city/area, geo, cuisines, rating, popularity, delivery economics, vertical and a 0–100 lead score) — ideal for food-tech, POS, delivery-SaaS, ghost-kitchen and supplier prospecting.

## `minRating` (type: `number`):

Only keep restaurants with a Talabat rating at or above this value. 0 = keep all.

## `vendorType` (type: `string`):

Restrict to restaurants or to grocery/retail stores (Talabat Mart, pharmacies, etc.). `All` returns everything.

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

Two-letter language code for content (menu item names, etc.): `en` (English) or `ar` (Arabic). Defaults to English.

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

Remember restaurants & reviews seen in previous runs (in a named key-value store) and emit only NEW ones and restaurants whose rating, delivery fee, minimum order, status or menu price range changed (tagged with `changeType`). Perfect for tracking a city/cuisine 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' ids/fingerprints for monitoring mode. Use a different name per tracked feed to keep histories separate. Lowercase letters, digits and hyphens only.

## `maxAreaPages` (type: `integer`):

How many result pages (15 restaurants each) to paginate per delivery area before moving on. Raise to exhaust a large area.

## `maxAreasPerCity` (type: `integer`):

When discovering by city, how many of that city's delivery areas to crawl (each area returns the restaurants delivering there). One central area usually covers most of a city.

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

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

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

Proxy settings. Apify Proxy is recommended. The default datacenter proxy works with Talabat; switch to RESIDENTIAL (country AE/SA/etc.) only if you see rate-limiting/blocks 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
{
  "country": "uae",
  "searchQueries": [
    "burger"
  ],
  "maxRestaurants": 60,
  "includeMenu": true,
  "includeItemDetails": true,
  "includeReviews": false,
  "maxReviewsPerRestaurant": 20,
  "includeMerchantLeads": true,
  "minRating": 0,
  "vendorType": "all",
  "language": "en",
  "monitorMode": false,
  "monitorStoreName": "talabat-monitor",
  "maxAreaPages": 3,
  "maxAreasPerCity": 2,
  "maxConcurrency": 6,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

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

All scraped records (restaurants with optional menus, reviews and merchant leads) 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 = {
    "searchQueries": [
        "burger"
    ],
    "urlsFromFile": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/talabat-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 = {
    "searchQueries": ["burger"],
    "urlsFromFile": "",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/talabat-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 '{
  "searchQueries": [
    "burger"
  ],
  "urlsFromFile": ""
}' |
apify call scrapesage/talabat-scraper --silent --output-dataset

```

## MCP server setup

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