Yemeksepeti Reviews API
Yemeksepeti Reviews API returns one JSON row per public review on a Yemeksepeti restaurant page: reviewText, ratingOverall, ratingFood, ratingRider, reviewerName, likes, vendorReply, createdAt and reviewUrl, in Turkish exactly as written. It covers restaurants across Turkey and costs $0.0015 per review ($1.50 per 1,000), falling to $1.20 per 1,000 on Gold and above. Run it in the Apify Console, via the API or as an MCP tool.
from $0.0015 per review, $1.50 per 1,000, down to $0.0012 on higher Apify plans · Updated Nov 2026, version 0.1.4
Key facts
- Price
- from $0.0015 per review, $1.50 per 1,000, down to $0.0012 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, version 0.1.4
- Actor
subimpact/yemeksepeti-reviews-api
Who it is for
- Turkish restaurant chains monitoring sentiment by branch
- Delivery and rider operations teams reading complaint text
- F&B analysts benchmarking competitors in Istanbul and Ankara
- NLP teams building Turkish sentiment datasets
Use cases
Sentiment across a chain
Pass one code per branch, for example awhi, and set maxReviewsPerVendor to 100. Rows carry ratingOverall and createdAt, so a weekly chart of average score per branch is a groupby away, and reviewText tells you what drove a drop. Because reviewId is a UUID per review, storing rows by that key keeps reruns from double counting.
Separate kitchen from courier
ratingFood and ratingRider are split where Yemeksepeti publishes them, and the ratings array lists every topic and its score. Filter to rows where the rider score is low but the food score is high and you have a delivery problem that a kitchen change would not fix. Group the count by vendorCode to see whether it is one branch or a city.
Read the replies
vendorReply holds the restaurant's public answer where one exists and null where it does not. Compare the share of replied rows against the rating band per vendorCode to see who answers one star reviews, and export reviewText with vendorReply as paired examples of recovery wording for a training deck or a chatbot prompt.
Discover a city first
Set locations to Istanbul, Ankara, Izmir, Antalya or Bursa, or a lat,lng pair, then choose maxRestaurantsPerLocation. The Actor takes the restaurants the platform lists near that point, in its own order, and each row then fills restaurantName, restaurantRating, restaurantReviewCount, restaurantCuisines and coordinates. Discovery itself is free; you pay only for the review rows that follow.
Build a Turkish review corpus
Set maxTotalReviews to your budget, minRestaurantReviews to skip restaurants with nothing to scrape, and let the Actor paginate. The result is natural Turkish review text with a star rating, a date and per-topic scores attached, which is the shape a sentiment classifier or a RAG index wants. Info and error rows carry no data and are never charged.
Output fields
| Field | Type | Description |
|---|---|---|
rowType | string/null | review for a review, info/error for a location note (never charged) |
platform | string/null | yemeksepeti (Turkey) |
country | string/null | Market code, tr for Yemeksepeti |
vendorCode | string/null | Restaurant code |
location | string/null | Discovery location this restaurant came from (null when you passed codes) |
reviewId | string/null | Unique review UUID |
reviewText | string/null | Full review text |
reviewerName | string/null | Display name of reviewer (or 'Anonymous') |
reviewerId | string/null | Reviewer identifier |
isAnonymous | boolean/null | Whether the reviewer chose to stay anonymous |
ratingOverall | integer/null | Overall star rating (1-5) |
ratingFood | integer/null | Food score (1-5) when present |
Show all 25 fields
| Field | Type | Description |
|---|---|---|
ratingRider | integer/null | Rider score (1-5) when present |
ratings | array/null | Full per-topic ratings array |
likes | integer/null | Helpful/like count |
vendorReply | string/null | Vendor reply text when present |
createdAt | string/null | Review creation timestamp (ISO) |
reviewUrl | string/null | Public review page URL |
restaurantName | string/null | Restaurant name from the listing (null when you passed codes) |
restaurantRating | number/null | Restaurant average rating from the listing, e.g. 4.5 |
restaurantReviewCount | integer/null | How many reviews the restaurant has in total, from the listing |
restaurantCuisines | array/null | Cuisine names from the listing |
restaurantLatitude | number/null | Restaurant latitude from the listing |
restaurantLongitude | number/null | Restaurant longitude from the listing |
error | string/null | Message on info/error rows (a location that could not be used); null on review rows |
Sample output
From one of our own test runs on 20 Nov 2026, trimmed. Personal data is redacted.
2 rows, first 3 shown
[
{
"rowType": "review",
"platform": "yemeksepeti",
"vendorCode": "awhi",
"country": "tr",
"reviewId": "ce345708-2ff8-5ba6-ac33-b9cfcc26011a",
"reviewText": "Annanem için söyledim. Çok beğendi.",
"reviewerName": "...I",
"reviewerId": "trtzwdem",
"isAnonymous": false,
"ratingOverall": 5,
"ratingFood": 5,
"ratingRider": 5,
"ratings": [
{
"topic": "overall",
"score": 5
},
{
"topic": "restaurant_food",
"score": 5
},
{
"topic": "rider",
"score": 5
}
],
"likes": 0,
"vendorReply": "afiyet olsun yine bekleriz",
"createdAt": "2026-11-19T14:59:46Z",
"reviewUrl": "https://www.yemeksepeti.com/restaurant/awhi/reviews",
"restaurantName": null,
"restaurantRating": null,
"restaurantReviewCount": null,
"restaurantCuisines": null,
"restaurantLatitude": null,
"restaurantLongitude": null,
"location": null,
"error": null
},
{
"rowType": "review",
"platform": "yemeksepeti",
"vendorCode": "awhi",
"country": "tr",
"reviewId": "b5a09348-db07-5178-878a-55fb6cc42351",
"reviewText": "Çok lezzetli ve güzel hazırlanmıştı. Notların dikkate alınması çok güzel.",
"reviewerName": "...I",
"reviewerId": "trtzwdem",
"isAnonymous": false,
"ratingOverall": 5,
"ratingFood": 5,
"ratingRider": 5,
"ratings": [
{
"topic": "overall",
"score": 5
},
{
"topic": "restaurant_food",
"score": 5
},
{
"topic": "rider",
"score": 5
}
],
"likes": 0,
"vendorReply": "afiyet olsun yine bekleriz",
"createdAt": "2026-11-19T14:59:23Z",
"reviewUrl": "https://www.yemeksepeti.com/restaurant/awhi/reviews",
"restaurantName": null,
"restaurantRating": null,
"restaurantReviewCount": null,
"restaurantCuisines": null,
"restaurantLatitude": null,
"restaurantLongitude": null,
"location": null,
"error": null
}
]Input
| Field | Type | Required | Description | Default |
|---|---|---|---|---|
vendorCodes | array | No | One or more Yemeksepeti restaurant codes (e.g. awhi). The code is the short segment in a restaurant URL: https://yemeksepeti.com/restaurant//. You can also paste full restaurant URLs, codes are extracted automatically. Leave empty to use... | - |
vendorUrls | array | No | 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 | array | No | 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... | - |
maxRestaurantsPerLocation | integer | No | How many restaurants to take from the listing for each location (1-500). Only used in discovery mode. | 20 |
minRestaurantReviews | integer | No | Skip restaurants that have fewer reviews than this in the listing (0 = keep all). Useful to avoid tiny/new restaurants with nothing to scrape. | 0 |
country | string | No | Yemeksepeti runs in Turkey only, so this is fixed to tr. The reviews API is reviews-api-tr.fd-api.com. | tr |
maxReviewsPerVendor | integer | No | Maximum number of reviews to fetch per restaurant. 0 = all available (paginate until exhausted). | 0 |
maxVendors | integer | No | Maximum number of restaurants to process after discovery or from your code list. 0 = all. | 0 |
maxTotalReviews | integer | No | 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. | 100 |
Example input
{
"vendorCodes": [
"awhi"
],
"locations": [
"Istanbul"
],
"country": "tr",
"maxTotalReviews": 100
}Pricing
| Event | What it means | Price | Lowest tier |
|---|---|---|---|
review | One Yemeksepeti review delivered to the dataset (text, ratings, reviewer, reply, restaurant context where known). Platform usage included. | $0.0015 | $0.0012 |
$1.50 at the listed price, or $1.20 on higher Apify plans, for 1,000 reviews.
Prices from the Apify Store on 20 November 2026. 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. Every row is a live listing on the Store, read on 20 Nov 2026, so a buyer can check each number at the source.
| Actor | Price per 1,000 reviews (Free plan) | Higher plans (Gold) | Start fee per run | Platform usage | Users | Rating | Last build |
|---|---|---|---|---|---|---|---|
| Yemeksepeti Reviews Scraper — Ratings, Comments & Replies This API | $1.50 | $1.20 | None | Included | 3 | No reviews yet | 20 Nov 2026 |
| Yemeksepeti Scraper — Restaurants, Menus & Prices | Charges per vendor scraped, plus an Actor start charge, and returns no reviews. | $0.00005 | Included | 22 | No reviews yet | 8 Nov 2026 | |
| Food Delivery Scraper | $2.00 | $0.7 | $0.0001 | Included | 65 | 5.0 (3 reviews) | 11 Nov 2026 |
Where Yemeksepeti Scraper — Restaurants, Menus & Prices is stronger
Where Yemeksepeti Scraper — Restaurants, Menus & Prices is stronger
- Returns restaurant and menu data with menu item prices, which we do not cover
- Can sweep a whole city using an optional geo grid
- Accepts coordinates as well as city names as a starting point
Where this API is stronger
- Returns review text, per topic ratings and restaurant replies
- Can start from restaurant codes, restaurant URLs or a list of cities
- Restaurant rating, review count and cuisines travel with each review row
Where Food Delivery Scraper is stronger
Where Food Delivery Scraper is stronger
- Covers many food delivery platforms, not only Yemeksepeti
- Can return menus and restaurant details in the same run
- Separate events let a mixed job cover listings, menus and reviews together
Where this API is stronger
- Focused on Yemeksepeti reviews, with food, rider and overall ratings on each row
- Restaurant replies and review likes are captured alongside the text
- Plain HTTP, so no browser rendering charge is added per item
Both alternatives serve a wider job than review collection: one covers Yemeksepeti restaurants and menus, the other spans many delivery platforms with reviews as one of several events. Buyers who need menu prices or multi platform coverage will prefer them, while anyone collecting Yemeksepeti review text with topic ratings, replies and restaurant context is best served here.
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.
How to run it
- Open a restaurant on yemeksepeti.com; the URL looks like https://yemeksepeti.com/restaurant/awhi/eyup-sultan-sofrasi-awhi.
- Copy the four character code awhi into vendorCodes, or paste the whole URL into vendorUrls and the code is extracted for you.
- Or set locations to Istanbul and maxRestaurantsPerLocation to 2 to find restaurants near that point first.
- Set maxReviewsPerVendor, for example 100, and maxTotalReviews as a ceiling for the whole run.
- Start the run in the Apify Console and open the dataset; one row per review appears with its ratings and reply.
- Export as JSON, CSV or Excel, or read the dataset through the Apify API.
cURL
curl -X POST "https://api.apify.com/v2/acts/subimpact~yemeksepeti-reviews-api/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"vendorCodes":["awhi"],"locations":["Istanbul"],"country":"tr","maxTotalReviews":100}'Python
from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/yemeksepeti-reviews-api").call(run_input={"vendorCodes":["awhi"],"locations":["Istanbul"],"country":"tr","maxTotalReviews":100})
for item in client.dataset(run["default_dataset_id"]).iterate_items():
print(item)JavaScript
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('subimpact/yemeksepeti-reviews-api').call({"vendorCodes":["awhi"],"locations":["Istanbul"],"country":"tr","maxTotalReviews":100});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);n8n
Use the Apify node (Run an Actor).
Actor ID: subimpact/yemeksepeti-reviews-api
Input JSON: paste the example input above.Limits
- Turkey only: the country input is fixed to tr.
- Older review pages depend on the platform's paging cursor, so a large per-restaurant cap may deliver fewer rows.
- Reviews vary by restaurant, and an empty result is normal for new or small outlets.
- Codes or URL inputs leave the restaurant context fields null; those are only filled in discovery mode.
Questions people ask
What does each review cost?
$0.0015 per review, which is $1.50 per 1,000 reviews on the Free plan, dropping to $1.20 per 1,000 on Gold and above. Only delivered reviews are charged, compute is included in the price, and discovery plus info and error rows are free.
Where does Yemeksepeti operate?
Turkey only. Yemeksepeti runs in Turkey alone, so the country input is fixed to tr, and discovery cities are Istanbul, Ankara, Izmir, Antalya and Bursa, or any lat,lng point you supply. Foodpanda, Talabat and foodora have their own actors for their markets.
Do I need a login?
No. The Actor reads the public review surface over plain HTTP with no browser, no account and no checkout access. Reviewer names appear as Yemeksepeti shows them publicly, including Anonymous where it hides the name.
Why did a restaurant return fewer reviews than the cap?
A reviews page holds up to 30 reviews and older pages depend on the platform's paging cursor. When the cursor stops moving forward the Actor ends that restaurant rather than repeating rows, so a large maxReviewsPerVendor can deliver less. New or small restaurants may return nothing at all.
Does the review text stay in Turkish?
Yes. reviewText is exactly what the customer wrote, with no translation or normalisation, and the ratings array holds the per-topic scores alongside it. That makes the dataset usable as Turkish-language training data as well as for reporting.
What is in the restaurant fields?
In discovery mode you get restaurantName, restaurantRating, restaurantReviewCount, restaurantCuisines, restaurantLatitude and restaurantLongitude plus the location it came from. When you pass a code or a URL instead, those fields are null, because a code does not carry the restaurant's details.
Can I schedule it monthly?
Yes. Apify schedules rerun the same input, and each row has createdAt plus a stable reviewId, so a new snapshot can be diffed against the last one. Keep maxTotalReviews modest for a recurring job and raise it when a branch starts generating a lot of feedback.
Need a data source that is not here?
We build and run scrapers for sites that have no public API. Tell us the site, the fields and how often you need them.