Yemeksepeti Reviews Scraper — Ratings, Comments & Replies avatar

Yemeksepeti Reviews Scraper — Ratings, Comments & Replies

Pricing

from $1.20 / 1,000 reviews

Go to Apify Store
Yemeksepeti Reviews Scraper — Ratings, Comments & Replies

Yemeksepeti Reviews Scraper — Ratings, Comments & Replies

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.

Pricing

from $1.20 / 1,000 reviews

Rating

0.0

(0)

Developer

subimpact network

subimpact network

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

18 hours ago

Last modified

Features

Limited permissions

Share

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: 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)

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

Example input (restaurant codes)

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

Input

FieldTypeDescription
vendorCodesstring[]Restaurant codes, e.g. awhi. URLs are accepted too. Prefilled with a working sample restaurant.
vendorUrlsstring[]Full yemeksepeti.com restaurant URLs. Codes are extracted automatically.
locationsstring[]Discovery: a city preset (Istanbul, Ankara, Izmir, Antalya, Bursa) or a lat,lng pair. Ignored when codes or URLs are given.
maxRestaurantsPerLocationintDiscovery: how many restaurants to take per location (1 to 500, default 20).
minRestaurantReviewsintDiscovery: skip restaurants with fewer reviews than this in the listing (default 0, keep all).
countrystringFixed to tr; Yemeksepeti runs in Turkey only.
maxReviewsPerVendorintCap per restaurant (0 = all).
maxVendorsintCap the number of restaurants processed (0 = all).
maxTotalReviewsintSafety cap on total reviews delivered across the whole run (default 100, 0 = unlimited).

Output (one row per review)

FieldDescription
rowTypereview for a review, info or error for a location note (notes are never charged)
platformyemeksepeti
countrytr
vendorCodeRestaurant code
reviewIdReview UUID
reviewTextFull review text
reviewerNameReviewer display name as Yemeksepeti shows it (or Anonymous)
reviewerIdReviewer identifier
isAnonymousAnonymous flag
ratingOverallOverall star rating (1 to 5)
ratingFoodFood score (1 to 5) when present
ratingRiderRider score (1 to 5) when present
ratingsFull per-topic ratings array
likesLike/helpful count
vendorReplyRestaurant reply text when there is one
createdAtReview timestamp (ISO)
reviewUrlReview page URL for the restaurant
restaurantNameRestaurant name (discovery mode)
restaurantRatingRestaurant average rating, e.g. 4.6 (discovery mode)
restaurantReviewCountTotal reviews the restaurant has (discovery mode)
restaurantCuisinesCuisine names (discovery mode)
restaurantLatitude, restaurantLongitudeRestaurant coordinates (discovery mode)
locationThe location this restaurant came from (discovery mode)
errorMessage on info/error rows, otherwise null

Example output row

A real row from the example discovery run above:

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

ActorWhat you getPrice 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-scraperRestaurants and menus, vendor-scraped, no reviews$3.00$1.50
e-commerce/food-delivery-scraperMulti-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.