# Talabat Reviews API

Talabat Reviews API returns one JSON row per public Talabat restaurant review: reviewText, rating, reviewerFirstName, reviewDate and reviewDateIso, plus the restaurant's name, slug, aggregate rating, total ratings and cuisines. It covers the UAE, Kuwait, Saudi Arabia, Bahrain, Oman, Qatar, Jordan, Egypt and Iraq, and costs $0.0005 per review ($0.50 per 1,000). Run it in the Apify Console, via the API or as an MCP tool.

## Key facts

- Price: from $0.0005 per review, $0.5 per 1,000, down to $0.00035 on higher Apify plans
- Pricing model: Pay per event
- Output: JSON, CSV, Excel, XML, RSS via Apify datasets
- Access: Apify Console, REST API, Python and JS clients
- Version: Updated Nov 2026, build 0.1.4
- Usage: 100.0% successful runs (30 days)
- Actor: subimpact/talabat-reviews-api

## Who it is for

- Restaurant groups monitoring reputation across MENA markets
- F&B analysts studying delivery quality and packaging complaints
- Competitor researchers benchmarking on the same marketplace
- Data teams assembling Arabic and English review corpora

## Use cases

### Collect only negative feedback

Set minRating to 1 and maxRating to 2 and the Actor delivers just the low star reviews, with rows filtered out neither delivered nor charged. Each row still carries reviewText, reviewDateIso and restaurantName, so a support team can work a queue of complaints per branch without wading through praise. Swap the range to 4 and 5 when you want reviews worth quoting in marketing.

### Benchmark against rivals

Pass several restaurant URLs from the same country, for example two UAE burger chains, and every row carries restaurantRating, restaurantTotalRatings and cuisines alongside the review itself. That lets you compare average rating, review volume and the wording of complaints across competitors on the same marketplace, rather than across platforms with different rating behaviour.

### Track a branch over time

reviewId is a hash of vendor id, date, first name, rating and text, so it stays stable across runs even though Talabat's own id is always 0. Store rows by that key and schedule the Actor monthly with maxReviewsPerRestaurant set to 100; new rows are the recent reviews, and the aggregate restaurantRating on each row shows whether the trend is up or down.

### Build a MENA review corpus

Talabat publishes reviews in the language the customer wrote, so a UAE or Saudi run returns Arabic and English text side by side, each with a star rating and a date. Use the rating plus reviewDateIso as labels, keep reviewText as the sample, and cap the run with maxItems. The facts record written reviews going back to January 2022 for the restaurants tested.

### Monitor delivery complaints

Search reviewText for terms about packaging, temperature or the rider, then group counts by vendorId and page. Because the Actor pages through reviews newest first, the first page is the recent window, which is what an operations team reacts to. An input that cannot be scraped produces a single uncharged error row, so one bad URL does not hide the rest of the run.

## Price events

- Review (`review`): $0.0005, lowest tier $0.00035. One Talabat review row delivered to the dataset

Prices from the Apify Store. Apify shows the final price before each run.

## How it compares with other Apify actors

Price per 1,000 reviews at Apify Store list prices, checked 20 Nov 2026.

| Actor | Price per 1,000 reviews (Free plan) | Higher plans (Gold) | Start fee per run | Platform usage | Users | Rating | Last build |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Talabat Reviews Scraper: Review Text, Ratings & Dates (this API) | $0.5 | $0.35 | None | Included | 3 | No reviews yet | 18 Nov 2026 |
| [Talabat Scraper - Restaurants, Menus, Prices & Leads](https://apify.com/scrapesage/talabat-scraper) | $1.00 | $0.7 | None | Included | 25 | No reviews yet | 5 Nov 2026 |
| [Talabat Scraper: Restaurant Menus, Prices, Reviews](https://apify.com/automation_craft/talabat-scraper) | $0.2 | $0.12 | $0.004 | Included | 17 | No reviews yet | 20 Nov 2026 |

### Where Talabat Scraper - Restaurants, Menus, Prices & Leads is stronger

- Also returns restaurants with menus, delivery fees and merchant leads
- Monitoring mode that emits only new or changed data
- Country, city and area targeting across the region

### Where this API is stronger

- Reviews first: one row per review with text, star rating, reviewer name and ISO date
- Filters on minimum and maximum rating for the reviews pulled
- Plain HTTP with no browser, so runs start quickly

### Where Talabat Scraper: Restaurant Menus, Prices, Reviews is stronger

- Full menu with dish prices and previous prices nested in restaurant rows
- Exact review figures and review statistics as optional outputs
- Dish level rows and chain level figures for menu analysis

### Where this API is stronger

- One clean row per review with a stable review id
- Rating filters applied to the reviews themselves
- No start fee before the first review row

Only a handful of actors cover Talabat at all, and both of the serious ones are restaurants-first scrapers that also return reviews as one event among several. This actor is reviews-first: one row per review with its text, rating and date, no menu or restaurant plumbing to pay for. Pick the broader scrapers when menus and leads matter too.

Prices are Apify Store list prices, checked 20 Nov 2026. Platform usage 'Paid separately' means Apify bills compute on top of the event price. Check each listing before you buy.

## Input

- `restaurantUrls` (array, optional): Talabat restaurant page URLs, one per line, e.g. https://www.talabat.com/uae/mcdonalds. Supported country segments: uae, kuwait, ksa, bahrain, oman, qatar, jordan, egypt, iraq. Query strings and trailing slashes are ignored. Leave empty ...
- `vendorIds` (array, optional): Numeric Talabat vendor IDs (e.g. 40701), used directly without loading the restaurant page. Restaurant fields are left null in the output for these rows. Leave empty when you use restaurant URLs instead.
- `maxReviewsPerRestaurant` (integer, optional): Upper limit of reviews to deliver for each restaurant. Reviews come newest first. Default 100 (one page).
- `maxItems` (integer, optional): Global cap on the number of review rows delivered in the whole run, across every input. Protects against a bigger bill than expected. Rows removed by the rating filter do not count toward it.
- `minRating` (integer, optional): Optional. Only deliver reviews with at least this many stars (1 to 5). Filtered rows are not charged.
- `maxRating` (integer, optional): Optional. Only deliver reviews with at most this many stars (1 to 5). Combine with Minimum rating to collect only negative or only positive feedback. Filtered rows are not charged.
- `proxyConfiguration` (object, optional): Talabat answers Apify's own network, so the default (no proxy) is the fastest and cheapest option. Apify DATACENTER proxies are blocked by Cloudflare; Apify RESIDENTIAL proxies work. If a direct request is blocked, the Actor retries it t...

### Example input

```json
{
  "restaurantUrls": [
    "https://www.talabat.com/uae/mcdonalds"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

## Output fields

- `vendorId` (string/null): Talabat vendor ID the reviews endpoint takes (e.g. 40701). Null on an error row for a URL that could not be resolved.
- `restaurantId` (string/null): Talabat restaurant ID from the restaurant page. Null for vendor-ID inputs.
- `restaurantName` (string/null): Restaurant name from the restaurant page. Null for vendor-ID inputs.
- `restaurantSlug` (string/null): Restaurant slug used in the Talabat URL. Null for vendor-ID inputs.
- `country` (string/null): Talabat country segment: uae, kuwait, ksa, bahrain, oman, qatar, jordan, egypt or iraq. Null for vendor-ID inputs.
- `restaurantUrl` (string/null): Canonical Talabat restaurant page URL. Null for vendor-ID inputs.
- `restaurantRating` (number/null): Aggregate restaurant rating shown on the page (e.g. 4.7).
- `restaurantTotalRatings` (integer/null): Number of ratings behind the aggregate rating.
- `cuisines` (string/null): Comma separated cuisine list from the restaurant page.
- `reviewId` (string/null): Stable review ID generated by this Actor (SHA-1 of vendorId, date, first name, rating and review text). Talabat's own review id is always 0.
- `reviewerFirstName` (string/null): Reviewer first name as published by Talabat.
- `rating` (integer/null): Star rating of the review, 1 to 5.
- `reviewText` (string/null): Review text as published (may be empty or only whitespace).
- `reviewDate` (string/null): Review date exactly as Talabat returns it, e.g. '16 October 2026'.
- `reviewDateIso` (string/null): Review date as YYYY-MM-DD, or null when the date could not be parsed.
- `page` (integer/null): 1-based reviews page the row came from.
- `scrapedAt` (string/null): ISO timestamp of the run that produced the row.
- `input` (string/null): The restaurant URL this row belongs to. Set on error rows for inputs that could not be resolved.
- `error` (string/null): Set on error rows: why this input could not be scraped. Error rows are never charged.

## Sample output

Trimmed from one of our own test runs. Personal data is redacted.

```json
[
  {
    "vendorId": "13822",
    "restaurantId": "4621",
    "restaurantName": "McDonald's",
    "restaurantSlug": "mcdonalds",
    "country": "uae",
    "restaurantUrl": "https://www.talabat.com/uae/mcdonalds",
    "restaurantRating": 3.9,
    "restaurantTotalRatings": 8426,
    "cuisines": "Fast Food, Sandwiches, Burgers",
    "reviewId": "649f4460f6936b2d4f9b7f311e989dffc8ddc0f4",
    "reviewerFirstName": "Hamda",
    "rating": 5,
    "reviewText": "يمي",
    "reviewDate": "22 October 2022",
    "reviewDateIso": "2022-10-22",
    "page": 1,
    "scrapedAt": "2026-11-20T02:46:33.691Z",
    "input": null,
    "error": null
  },
  {
    "vendorId": "13822",
    "restaurantId": "4621",
    "restaurantName": "McDonald's",
    "restaurantSlug": "mcdonalds",
    "country": "uae",
    "restaurantUrl": "https://www.talabat.com/uae/mcdonalds",
    "restaurantRating": 3.9,
    "restaurantTotalRatings": 8426,
    "cuisines": "Fast Food, Sandwiches, Burgers",
    "reviewId": "3e4f44dac9bad5ed76ddcb2b3619e41a18465616",
    "reviewerFirstName": "صالح",
    "rating": 3,
    "reviewText": "The cola is water because they put more ice",
    "reviewDate": "18 October 2022",
    "reviewDateIso": "2022-10-18",
    "page": 1,
    "scrapedAt": "2026-11-20T02:46:33.691Z",
    "input": null,
    "error": null
  }
]
```

## How to run it

1. Find a restaurant on talabat.com and copy its URL, for example https://www.talabat.com/uae/burger-hut, or use a numeric vendor ID such as 40701.
2. Paste one or more into restaurantUrls or vendorIds, then set maxReviewsPerRestaurant, 100 by default, and maxItems, 1000 by default.
3. Optional: set minRating and maxRating to keep only the star band you care about; filtered rows are not charged.
4. Leave proxyConfiguration empty, which runs direct and works; a residential proxy is the fallback if a request is blocked.
5. Start the run in the Apify Console; one row per review appears, newest first, with the restaurant context attached.
6. Export as JSON, CSV or Excel, or read the dataset through the Apify API.

### cURL

```bash
curl -X POST "https://api.apify.com/v2/acts/subimpact~talabat-reviews-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"restaurantUrls":["https://www.talabat.com/uae/mcdonalds"],"proxyConfiguration":{"useApifyProxy":false}}'
```

### Python

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/talabat-reviews-api").call(run_input={
      "restaurantUrls": [
        "https://www.talabat.com/uae/mcdonalds"
      ],
      "proxyConfiguration": {
        "useApifyProxy": false
      }
    })

for item in client.dataset(run["default_dataset_id"]).iterate_items():
    print(item)
```

### JavaScript

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

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('subimpact/talabat-reviews-api').call({
  "restaurantUrls": [
    "https://www.talabat.com/uae/mcdonalds"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();

console.log(items);
```

### n8n

Use the Apify node (Run an Actor).
Actor ID: subimpact/talabat-reviews-api
Input JSON: paste the example input below.

## Limits

- Only written reviews are returned; ratings without text never appear.
- Reviews older than those Talabat still serves, around January 2022 in the recorded test, are not available.
- A restaurant URL resolves to the branch Talabat serves for it, so multi-branch chains may need one vendor ID per branch.
- Datacenter proxies are blocked by Cloudflare; the default is a direct request, with residential as the fallback.

## FAQ

### What is the price per review?

$0.0005 per review, which is $0.50 per 1,000 reviews on the Free plan, with a lower published rate on paid plans. Only delivered rows are charged: error rows and rows removed by the rating filter cost nothing, and platform usage is included in the event price.

### Which countries does it cover?

All nine Talabat country sites: the UAE, Kuwait, Saudi Arabia, Bahrain, Oman, Qatar, Jordan, Egypt and Iraq. The country is read from the first path segment of the restaurant URL, so you can mix markets in one run as long as each URL carries its own country.

### Does it return every rating or only reviews with text?

Only written reviews. The review list Talabat serves carries reviews with text, so star ratings left without a comment do not appear. In the sample restaurant the page showed 1,000 ratings against roughly 300 written reviews, which is a normal ratio.

### Why does a restaurant return no rows?

Many restaurants have few or no written reviews. In a test of 13 UAE and Egypt pages, 6 returned reviews and 7 returned none, so an empty result is normal rather than a failure. No rows means no charge, and the run log says so.

### How far back do the reviews go?

In the recorded test, written reviews went back to January 2022 and Talabat did not return older ones. The Actor keeps Talabat's newest-first order and pages until maxReviewsPerRestaurant, maxItems or the end of the list, so age is bounded by what the platform still serves.

### Do I need a login or a proxy?

No login: reviews are public and the Actor runs over plain HTTP at 256 MB. No proxy is the default and it works. Datacenter proxies are blocked by Cloudflare, so if a direct request is blocked the Actor retries through a residential session and logs a warning.

### Is reviewId a Talabat identifier?

No. Talabat's own review id is always 0, so the Actor generates reviewId as a hash of vendor id, date, first name, rating and text. It is stable across runs for the same review, which makes it usable as a deduplication key, but it will not match anything on Talabat's side.

## Links

- Page: https://subimpact.net/apis/talabat-reviews-api/
- Category: https://subimpact.net/apis/category/food-delivery/
- Run on Apify: https://apify.com/subimpact/talabat-reviews-api
- All data APIs: https://subimpact.net/apis/
- Catalogue JSON: https://subimpact.net/apis/catalogue.json
