# Yemeksepeti Reviews Scraper — Ratings, Comments & Replies (`subimpact/yemeksepeti-reviews-api`) Actor

Scrape Yemeksepeti restaurant reviews in Turkey: review text, overall/food/rider ratings, reviewer, date, likes and restaurant replies. Input restaurant codes, URLs or a city (Istanbul, Ankara, Izmir). Plain HTTP, no login. $1.50 per 1,000 reviews, platform usage included.

- **URL**: https://apify.com/subimpact/yemeksepeti-reviews-api.md
- **Developed by:** [subimpact network](https://apify.com/subimpact) (community)
- **Categories:** E-commerce, Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 reviews

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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Yemeksepeti Reviews Scraper

Scrape **restaurant reviews** from Yemeksepeti across Turkey: review text, per-topic ratings (overall, food, rider), reviewer name, dates, likes and restaurant replies. Search by restaurant code, or point the Actor at a city and let it find the restaurants there first.

This Actor is **reviews-first**. It returns the actual review text and the per-topic scores, not just an aggregate rating number.

Need the restaurant list, menus and prices too? Use [Yemeksepeti Scraper: Restaurants, Menus & Prices](https://apify.com/subimpact/yemeksepeti-scraper): one row per restaurant with rating, fees and offers, plus one row per menu item size with TRY prices.

### Why use this Actor

- **Review text plus ratings**: overall, food and rider scores come from the same public review records, along with the reviewer display name, likes and the restaurant's reply.
- **Discovery mode**: give `Istanbul` (or `41.0082,28.9784`) and the Actor lists restaurants near that point, then scrapes their reviews. Every row carries the restaurant name, rating, review count, cuisines and coordinates.
- **Simple input**: paste a restaurant code or a full restaurant URL. The code and the market are read for you.
- **Public review surface only**: no login, no account data, no checkout.

### How to use

1. Open a restaurant page on yemeksepeti.com. The URL looks like `https://yemeksepeti.com/restaurant/awhi/eyup-sultan-sofrasi-awhi`.
2. Either copy the four-character code (`awhi`) into **Restaurant codes**, or paste the whole URL into **Restaurant URLs**.
3. Or skip codes: put `Istanbul` in **Locations** and choose how many restaurants you want.
4. Start the run.

#### Example input (discovery mode)

```json
{
  "locations": ["Istanbul"],
  "maxRestaurantsPerLocation": 2,
  "maxTotalReviews": 20
}
```

#### Example input (restaurant codes)

```json
{
  "vendorCodes": ["awhi"],
  "maxReviewsPerVendor": 100
}
```

#### Input

| Field | Type | Description |
|---|---|---|
| `vendorCodes` | string\[] | Restaurant codes, e.g. `awhi`. URLs are accepted too. Prefilled with a working sample restaurant. |
| `vendorUrls` | string\[] | Full yemeksepeti.com restaurant URLs. Codes are extracted automatically. |
| `locations` | string\[] | Discovery: a city preset (Istanbul, Ankara, Izmir, Antalya, Bursa) or a `lat,lng` pair. Ignored when codes or URLs are given. |
| `maxRestaurantsPerLocation` | int | Discovery: how many restaurants to take per location (1 to 500, default 20). |
| `minRestaurantReviews` | int | Discovery: skip restaurants with fewer reviews than this in the listing (default 0, keep all). |
| `country` | string | Fixed to `tr`; Yemeksepeti runs in Turkey only. |
| `maxReviewsPerVendor` | int | Cap per restaurant (0 = all). |
| `maxVendors` | int | Cap the number of restaurants processed (0 = all). |
| `maxTotalReviews` | int | Safety cap on total reviews delivered across the whole run (default 100, 0 = unlimited). |

#### Output (one row per review)

| Field | Description |
|---|---|
| `rowType` | `review` for a review, `info` or `error` for a location note (notes are never charged) |
| `platform` | `yemeksepeti` |
| `country` | `tr` |
| `vendorCode` | Restaurant code |
| `reviewId` | Review UUID |
| `reviewText` | Full review text |
| `reviewerName` | Reviewer display name as Yemeksepeti shows it (or `Anonymous`) |
| `reviewerId` | Reviewer identifier |
| `isAnonymous` | Anonymous flag |
| `ratingOverall` | Overall star rating (1 to 5) |
| `ratingFood` | Food score (1 to 5) when present |
| `ratingRider` | Rider score (1 to 5) when present |
| `ratings` | Full per-topic ratings array |
| `likes` | Like/helpful count |
| `vendorReply` | Restaurant reply text when there is one |
| `createdAt` | Review timestamp (ISO) |
| `reviewUrl` | Review page URL for the restaurant |
| `restaurantName` | Restaurant name (discovery mode) |
| `restaurantRating` | Restaurant average rating, e.g. 4.6 (discovery mode) |
| `restaurantReviewCount` | Total reviews the restaurant has (discovery mode) |
| `restaurantCuisines` | Cuisine names (discovery mode) |
| `restaurantLatitude`, `restaurantLongitude` | Restaurant coordinates (discovery mode) |
| `location` | The location this restaurant came from (discovery mode) |
| `error` | Message on `info`/`error` rows, otherwise null |

#### Example output row

A real row from the example discovery run above:

```json
{
  "rowType": "review",
  "platform": "yemeksepeti",
  "vendorCode": "vxuz",
  "country": "tr",
  "reviewId": "059ab53c-1a7a-524e-9a38-db397d886bdd",
  "reviewText": "Gayet lezzetliydi ama biraz çıtır olabilirdi :)",
  "reviewerName": "...a",
  "reviewerId": "trhf7rke",
  "isAnonymous": false,
  "ratingOverall": 5,
  "ratingFood": 5,
  "ratingRider": null,
  "ratings": [{ "topic": "overall", "score": 5 }, { "topic": "restaurant_food", "score": 5 }],
  "likes": 0,
  "vendorReply": null,
  "createdAt": "2026-11-07T16:02:45Z",
  "reviewUrl": "https://yemeksepeti.com/restaurant/vxuz/pasa-mevlana-pide/reviews",
  "restaurantName": "Paşa Mevlana Pide",
  "restaurantRating": 4.6,
  "restaurantReviewCount": 16692,
  "restaurantCuisines": ["Pide & Lahmacun", "Döner"],
  "restaurantLatitude": 41.005443,
  "restaurantLongitude": 28.936675,
  "location": "Istanbul",
  "error": null
}
```

When you pass codes or URLs instead of locations, the `restaurant*` fields and `location` are `null`.

### Discovery mode

For each location the Actor asks the platform which restaurants it lists near that point, keeps the first N in the platform's own order, optionally filters by review count, and then scrapes reviews for each restaurant. Restaurants that show up in more than one location are scraped once.

- A location the Actor cannot use (unknown city, bad coordinates) produces one `error` row, and the rest of the run continues.
- A location with no restaurants produces one `info` row.
- Discovery itself is not charged. You pay only for review rows.

### Use cases

- Sentiment and reputation monitoring for Turkish restaurant chains
- Food quality and delivery (rider) feedback analysis
- Competitor benchmarking across a city
- AI and RAG training data: Turkish review text with structured ratings

### Pricing

Pay per event: **$1.50 per 1,000 reviews** on the Free plan ($0.0015 per review), and lower prices on paid Apify plans: $1.40 (Bronze), $1.30 (Silver) and $1.20 (Gold and above) per 1,000. You only pay for reviews actually delivered. Platform usage (compute) is included in the event price, and the Actor runs on plain HTTP with no browser.

### How this compares

| Actor | What you get | Price per 1,000 items (Free plan) | Price per 1,000 items (Gold plan) |
|---|---|---|---|
| **subimpact/yemeksepeti-reviews-api** (this Actor) | Review text, per-topic ratings, reviewer, reply, restaurant context, included compute | $1.50 | $1.20 |
| hipersoft/yemeksepeti-scraper | Restaurants and menus, vendor-scraped, no reviews | $3.00 | $1.50 |
| e-commerce/food-delivery-scraper | Multi-platform; push-review event | $2.00 | $0.70 |

The hipersoft Actor also charges a start event of about $0.00005. Prices are Apify Store list prices as of 7 November 2026, Free-plan list prices, and can change.

### Notes and limitations

- This Actor collects **publicly visible review data** from Yemeksepeti's public review surface. Use it in accordance with Yemeksepeti's terms of service and local regulations. Reviewer names are shown as the platform itself shows them on the public page.
- Reviews availability varies by restaurant, and an empty result is normal for a new or small restaurant.
- Each reviews page holds up to 30 reviews. Older pages depend on the platform's own paging cursor; if the cursor stops moving forward the Actor ends that restaurant instead of repeating rows, so a large `maxReviewsPerVendor` may deliver fewer rows than you asked for.
- Restaurant codes are four characters. A code only works for its own restaurant.
- Not affiliated with Delivery Hero or Yemeksepeti.

### Run monitoring and privacy

If a run fails or times out, this Actor tells its developer the run ID and status, so we can fix problems fast. It never sends your input, your results or your account data.

# Actor input Schema

## `vendorCodes` (type: `array`):

One or more Yemeksepeti restaurant codes (e.g. awhi). The code is the short segment in a restaurant URL: https://yemeksepeti.com/restaurant/<CODE>/<slug>. You can also paste full restaurant URLs, codes are extracted automatically. Leave empty to use `locations` instead.

## `vendorUrls` (type: `array`):

Alternative to restaurant codes: paste full Yemeksepeti restaurant URLs, for example https://yemeksepeti.com/restaurant/awhi/eyup-sultan-sofrasi-awhi. Codes are extracted automatically.

## `locations` (type: `array`):

Find restaurants near a place instead of pasting codes. Each entry is a city preset name (Istanbul, Ankara, Izmir, Antalya, Bursa) or a "lat,lng" pair such as 41.0082,28.9784. Restaurants come back in the platform's own listing order for that point. Ignored when restaurant codes or URLs are given.

## `maxRestaurantsPerLocation` (type: `integer`):

How many restaurants to take from the listing for each location (1-500). Only used in discovery mode.

## `minRestaurantReviews` (type: `integer`):

Skip restaurants that have fewer reviews than this in the listing (0 = keep all). Useful to avoid tiny/new restaurants with nothing to scrape.

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

Yemeksepeti runs in Turkey only, so this is fixed to tr. The reviews API is reviews-api-tr.fd-api.com.

## `maxReviewsPerVendor` (type: `integer`):

Maximum number of reviews to fetch per restaurant. 0 = all available (paginate until exhausted).

## `maxVendors` (type: `integer`):

Maximum number of restaurants to process after discovery or from your code list. 0 = all.

## `maxTotalReviews` (type: `integer`):

Safety cap on the total number of reviews delivered across ALL restaurants in the run, protecting against unexpected bill size on wide inputs. Lower it or raise it freely; 0 = unlimited.

## Actor input object example

```json
{
  "vendorCodes": [
    "awhi"
  ],
  "locations": [
    "Istanbul"
  ],
  "maxRestaurantsPerLocation": 20,
  "minRestaurantReviews": 0,
  "country": "tr",
  "maxReviewsPerVendor": 0,
  "maxVendors": 0,
  "maxTotalReviews": 100
}
```

# Actor output Schema

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

One dataset item per review: rowType, platform, country, location, vendorCode, reviewId, reviewText, reviewerName, reviewerId, isAnonymous, ratingOverall, ratingFood, ratingRider, ratings (full per-topic array), likes, vendorReply, createdAt, reviewUrl, restaurantName, restaurantRating, restaurantReviewCount, restaurantCuisines, restaurantLatitude, restaurantLongitude, error.

# 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 = {
    "vendorCodes": [
        "awhi"
    ],
    "locations": [
        "Istanbul"
    ],
    "country": "tr",
    "maxTotalReviews": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("subimpact/yemeksepeti-reviews-api").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 = {
    "vendorCodes": ["awhi"],
    "locations": ["Istanbul"],
    "country": "tr",
    "maxTotalReviews": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("subimpact/yemeksepeti-reviews-api").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 '{
  "vendorCodes": [
    "awhi"
  ],
  "locations": [
    "Istanbul"
  ],
  "country": "tr",
  "maxTotalReviews": 100
}' |
apify call subimpact/yemeksepeti-reviews-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,subimpact/yemeksepeti-reviews-api"
        }
    }
}
```

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/tgwrGuWccDtzhiOrZ/builds/OxuzGJ6N1qyO6spWV/openapi.json
