Yemeksepeti Scraper: Restaurants, Menus & Prices
Pricing
from $1.20 / 1,000 restaurants
Yemeksepeti Scraper: Restaurants, Menus & Prices
Yemeksepeti restaurants by city or coordinates: rating, review count, delivery fee, minimum order, offers, opening hours. Menus mode adds one row per item size with TRY price, pre-discount price and options. No login. $1.50 per 1,000 restaurants, full menus +$1.00 per 1,000.
Pricing
from $1.20 / 1,000 restaurants
Rating
0.0
(0)
Developer
subimpact network
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
2
Monthly active users
18 hours ago
Last modified
Categories
Features
Share
Yemeksepeti restoran listesi, menü ve fiyat verisi (Türkiye). Restaurants by city or coordinates, and full menus with one row per orderable size, prices in TRY.
This Actor collects public Yemeksepeti data over plain HTTP. No browser, no login, no API key. One run can return restaurants from a city (rating, review counts, delivery fee, minimum order, offers, opening hours, coordinates) and, in menus mode, every item on their menus with its price, pre-discount price and discount percentage.
What you get
Every dataset item has a rowType, so one dataset holds both kinds of row:
restaurant: one row per restaurant. Code, id, name and URL, cuisines, rating, review counts, price level, address, city, coordinates, distance from your search point, minimum order, delivery fee, delivery time, open/active flags, chain, offer names, opening hours, logo, website, currency, search location and scrape time.menuItem(menus mode): one row per orderable size. Product, description, menu, category, size name, price, price before discount, discount percent, container price, sold out, alcoholic, vegetarian, popular flag, image URL and, withincludeOptions, the option groups of that item with option prices.error/info: a note about an input that could not be used (unknown restaurant code, a typo in a code list, an empty area). These rows are never charged.
Prices are in Turkish lira (currency: "TRY"), exactly as the platform publishes them at
scrape time.
Input example
This exact input works as written. It reads one restaurant's complete menu, including the option groups (extras, size choices) with their prices:
{"restaurantUrls": ["awhi"],"mode": "menus","includeOptions": true}
To discover restaurants instead of naming them, give one or more locations. City presets are
Istanbul, Ankara, Izmir, Antalya and Bursa; a "lat,lng" pair works too:
{"locations": ["Istanbul"],"maxRestaurants": 5,"minRating": 4.5}
An empty {} input runs the same thing with locations: ["Istanbul"] and
maxRestaurants: 20. proxyConfiguration keeps its default, the Apify residential proxy in
Turkey, which is what the menu requests need; you normally leave it alone.
restaurantUrls accepts restaurant URLs
(https://www.yemeksepeti.com/restaurant/awhi/eyup-sultan-sofrasi-awhi) or bare codes
(awhi). An entry that is neither becomes its own error row and the rest of the list is
still scraped.
Output examples
Real rows from a recorded run of the input above (field order kept, long arrays shortened):
{"rowType": "restaurant","restaurantCode": "awhi","restaurantId": 125626,"name": "Eyüp Sultan Sofrası","url": "https://www.yemeksepeti.com/restaurant/awhi/eyup-sultan-sofrasi-awhi","cuisines": ["Kebap & Türk Mutfağı", "Pide & Lahmacun"],"rating": 4.5,"reviewCount": 9590,"reviewWithCommentCount": 0,"priceLevel": 2,"address": "İmrahor İlyasbey Cd. No:68, Yedikule mah","city": "Istanbul","latitude": 40.9969589,"longitude": 28.928087,"distanceKm": null,"minimumOrderAmount": 0,"deliveryFee": 0,"deliveryTimeMinutes": null,"isActive": true,"isDeliveryEnabled": true,"isPickupEnabled": false,"isNew": false,"isPromoted": false,"chainName": null,"chainCode": null,"offers": ["Tüm ürünlerde %15"],"openingHours": [{ "weekday": 1, "opens": "11:00", "closes": "23:59" },{ "weekday": 1, "opens": "00:00", "closes": "04:00" }],"logoUrl": null,"website": null,"currency": "TRY","searchLocation": null,"scrapedAt": "2026-11-20T03:00:20.377Z"}
{"rowType": "menuItem","restaurantCode": "awhi","restaurantName": "Eyüp Sultan Sofrası","menuName": "Ana Menü","categoryName": "Ekonomik Menüler","productId": 73935904,"productName": "3'lü Lahmacun Menü","productDescription": "3 Adet Lahmacun + Ezme + Pepsi Max (33 cl.)","variationId": 82616906,"variationName": null,"price": 552.5,"priceBeforeDiscount": 650,"discountPercent": 15,"containerPrice": null,"isSoldOut": false,"isAlcoholic": false,"isVegetarian": false,"isPopular": false,"imageUrl": "https://yemeksepeti.dhmedia.io/image/fd-tr/Products/73935904.jpg","optionGroups": null,"currency": "TRY","scrapedAt": "2026-11-20T03:00:20.377Z"}
The same restaurant in a "locations": ["Istanbul"] run also fills distanceKm (for
example 4.403) and searchLocation (Istanbul), but openingHours stays null unless the
restaurant's detail is fetched. A size choice looks like this (variationName tells the two
sizes apart; the product has 2 sizes):
{"rowType": "menuItem","productName": "Kıymalı Pide","variationId": 44655295,"variationName": "1.5 Porsiyon","price": 552.5,"priceBeforeDiscount": 650,"discountPercent": 15,"isPopular": false,"currency": "TRY"}
With includeOptions an item also carries its option groups, here from a large pizza menu:
{"optionGroups": [{"groupName": "Ekstra Malzeme (Küçük Boy Pizza)","minSelect": 0,"maxSelect": 23,"options": [{ "name": "Yeşil Biber", "price": 15, "isSoldOut": false },{ "name": "Domates", "price": 15, "isSoldOut": false }]}]}
Pricing
Pay per event, no subscription, platform usage included:
restaurant: $1.50 per 1,000 restaurant rows.restaurant-menu: $1.00 per 1,000 restaurant menus. Charged once per restaurant, after its last menu item row, and only when at least one item row was delivered.
Menu item rows themselves are not charged, so a menu with 145 sizes costs the same as a menu
with 10. A full menu for one restaurant, like Eyüp Sultan Sofrası with 105 products and 145
orderable sizes, costs $0.0025 here. The default {} run (20 restaurants, restaurants mode)
costs $0.03. Proxy traffic is included in these prices. Error and info rows are never charged.
How this compares
Free-plan list prices from the Apify Store, checked 2026-11-20:
| Actor | Price | Notes |
|---|---|---|
| This actor | $1.50 / 1,000 restaurants; full menu +$1.00 / 1,000 restaurants | platform usage included, one row per item size |
| hipersoft/yemeksepeti-scraper | $3.00 / 1,000 restaurants (Free tier) | menu items included |
| teodor_banea/yemeksepeti-restaurant-menu-scraper | $2.00 / 1,000 rows + $0.005 per run start | one row per item size |
| dodoflix/yemeksepeti-scraper | $1.00 / 1,000 rows | every menu row is billed |
How it works and what the limits are
- Restaurants come from Yemeksepeti's public restaurant listing, one request per 50
restaurants.
maxRestaurantscaps a discovery run across all locations; restaurants are taken in the platform's listing order, so a small cap is the cheapest run. When you pass codes or URLs, every entry you give is scraped. - Detail fields (address, opening hours, website, logo, full menu) come from the public
vendor page data, one request per restaurant. Restaurants mode from a location uses listing
data only and leaves detail-only fields
nullto keep the run cheap. - Restaurant detail and menu requests go through the proxy you pick in
proxyConfiguration. The default is the Apify residential proxy in Turkey, which is the tested setting: the menu API sits behind a bot check that starts answering HTTP 403 to repeated requests from one datacentre IP. Proxy traffic is included in the price, there is no extra charge for it. - Discovery from a location needs no proxy: the listing endpoint is not behind that bot check,
so listing requests go out directly. A
{}run therefore sends no proxied request at all. - Every restaurant is fetched with its own proxy session. If the bot check answers anyway, the request is retried up to 4 more times, each with a new session, after 1, 2, 4 and 8 seconds. A restaurant that still fails becomes an uncharged error row and the run continues with the next one.
- If the proxy cannot be set up (for example your plan has no residential proxy access) you get
one uncharged
inforow explaining it, and the detail and menu requests fail with a clear message instead of being sent from the Actor's own IP, where the site would block them. Turning Apify Proxy off is a quick-test option only: direct menu requests may be blocked. gridRadiusKm/gridStepKmadd a square grid of points around each location, which surfaces more restaurants in a city. Duplicates are removed by restaurant code and the run stops atmaxRestaurants.searchQuerymatches restaurant names and cuisines, accent and case insensitive (donerfindsDöner).minRatingkeeps restaurants at or above a rating. Both filters apply to discovery.- Menus are the delivery menu of the restaurant (language
tr). An item with several sizes produces one row per size, because that is what a customer can order.isPopularis true when the platform tags the product as popular or puts it in a popular category. - Menus mode caps item rows per restaurant only if you set
maxMenuItemsPerRestaurant;0means the complete menu. - Every request has a 20 second timeout. Network errors, HTTP 429 and 5xx are retried 3 times with backoff. A 404 (unknown restaurant code) is reported as an error row and not retried. A block page (HTTP 403 from the site's bot check) is retried with a fresh proxy session, as described above.
- An unknown upstream response shape becomes an uncharged error row instead of made-up data. If the platform changes its public endpoints, the run reports the problem rather than inventing fields.
- The Actor is a plain Node.js program (512 MB is plenty). A local run that delivered 146 rows peaked at about 100 MB of memory.
- Yemeksepeti can change its public pages, prices or menus at any time; rows are a snapshot of
the moment of the run (
scrapedAt). This Actor is not affiliated with Yemeksepeti or Delivery Hero.
Need the reviews too? Yemeksepeti Reviews Scraper returns review text, ratings, reviewer info and vendor replies.
Responsible use
Collect only public menu and restaurant data, and use it for legitimate market, pricing or menu research. Do not use it to contact restaurants at scale, to build a competing listing that copies the platform's content wholesale, or in any way that breaks Yemeksepeti's terms or local law. Restaurant and menu data changes often, so date your snapshots.