Yemeksepeti Scraper
Yemeksepeti Scraper returns restaurant rows for Turkey with code, name, rating, reviewCount, cuisines, address, coordinates, minimumOrderAmount, deliveryFee, offers and openingHours, and in menus mode one row per orderable size with productName, price, priceBeforeDiscount, discountPercent and option groups in TRY. It costs $1.50 per 1,000 restaurants plus $1.00 per 1,000 menus, and runs in the Apify Console, API or MCP.
from $0.0015 per restaurant, $1.50 per 1,000, down to $0.0012 on higher Apify plans · Updated Nov 2026, version 0.1.1
Key facts
- Price
- from $0.0015 per restaurant, $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.1
- Actor
subimpact/yemeksepeti-scraper
Who it is for
- Restaurant chains benchmarking their own fees and prices
- Menu and pricing analysts tracking TRY prices by city
- Food-tech teams mapping a neighbourhood's restaurant supply
- Market researchers building a Turkish delivery catalogue
Use cases
Map a city's restaurants
Set locations to Istanbul, maxRestaurants to 20 and add minRating 4.5 to keep only well rated places. Every row carries rating, reviewCount, priceLevel, minimumOrderAmount, deliveryFee, offers, coordinates and distanceKm from your search point, which is enough for a supply map. gridRadiusKm widens the search around the city and duplicates are removed by restaurant code.
Track menu prices by size
Set mode to menus and pass a restaurant code such as awhi. Each orderable size becomes its own row with productName, variationName, price, priceBeforeDiscount and discountPercent in TRY, so a size upgrade and a base item are not conflated. Run the same list monthly and diff price by variationId to see which items moved and by how much.
Compare offers and fees
The restaurant row carries offers as a list, plus minimumOrderAmount, deliveryFee and deliveryTimeMinutes. Filter to restaurants running a promotion and compare their fee against others in the same cuisine and price level, which is how you tell whether an offer is funded by a higher delivery charge. city and chainName let you group the comparison by brand.
Build a menu catalogue with options
Turn on includeOptions and each item arrives with its optionGroups, including minSelect, maxSelect and the price of every extra. That is the detail needed to model a real order total rather than the headline price. maxMenuItemsPerRestaurant caps rows per restaurant if you only want the core menu, and sold out and vegetarian flags come with each item.
Find a niche by keyword
searchQuery matches restaurant names and cuisines without accent or case sensitivity, so doner finds Döner. Combine it with minRating and a city preset to build a shortlist of kebab or pide places in Ankara before pulling their menus, rather than scraping thousands of restaurants and filtering the rows afterwards.
Output fields
| Field | Type | Description |
|---|---|---|
rowType | string/null | restaurant, menuItem, or error/info for a note that is never charged |
inputValue | string/null | The location or restaurant entry a note row is about; null on result rows |
error | string/null | Why this input was skipped; null on result and info rows |
message | string/null | Informational note (for example: no restaurants matched); null on result and error rows |
restaurantCode | string/null | Yemeksepeti restaurant code, e.g. awhi (the short segment of the restaurant URL) |
restaurantId | integer/null | Numeric restaurant id |
name | string/null | Restaurant name |
url | string/null | Public Yemeksepeti restaurant page |
cuisines | array/null | Cuisine names, e.g. ["Kebap & Türk Mutfağı", "Pide & Lahmacun"] |
rating | number/null | Average star rating, e.g. 4.5 |
reviewCount | integer/null | Total number of reviews |
reviewWithCommentCount | integer/null | How many reviews carry a written comment |
Show all 40 fields
| Field | Type | Description |
|---|---|---|
priceLevel | integer/null | Price level 1-3 as shown by the platform (budget) |
address | string/null | Street address |
city | string/null | City name |
postCode | string/null | Postal code |
latitude | number/null | Restaurant latitude |
longitude | number/null | Restaurant longitude |
distanceKm | number/null | Distance from your search point, discovery only; null when you passed codes |
minimumOrderAmount | number/null | Minimum order amount in TRY (0 = none) |
deliveryFee | number/null | Delivery fee in TRY (0 = free delivery) |
deliveryTimeMinutes | number/null | Minimum delivery time in minutes when the platform publishes one |
isActive | boolean/null | Whether the restaurant is active on the platform |
isDeliveryEnabled | boolean/null | Whether delivery orders are accepted |
isPickupEnabled | boolean/null | Whether pickup orders are accepted |
isNew | boolean/null | Whether the platform marks the restaurant as new |
isPromoted | boolean/null | Whether the listing is a promoted placement |
chainName | string/null | Chain name when the restaurant belongs to a chain (e.g. Papa John's Pizza) |
chainCode | string/null | Chain code when the restaurant belongs to a chain |
offers | array/null | Active offer/discount names, e.g. ["Tüm ürünlerde %15"]; empty when none |
openingHours | array/null | Delivery schedule as [{weekday, opens, closes}], weekday 1 = Monday; null when unknown |
logoUrl | string/null | Restaurant logo image |
website | string/null | Restaurant website when the platform publishes one |
currency | string/null | Always TRY |
searchLocation | string/null | The location this restaurant was discovered from; null when you passed codes |
scrapedAt | string/null | ISO timestamp of this run |
restaurantName | string/null | Name of the restaurant the menu item belongs to |
menuName | string/null | Menu the item belongs to, e.g. Ana Menü |
categoryName | string/null | Menu category, e.g. Kebaplar |
productId | integer/null | Product id (shared by all sizes of the same product) |
Sample output
From one of our own test runs on 20 Nov 2026, trimmed. Personal data is redacted.
2 rows, first 3 shown
[
{
"rowType": "restaurant",
"restaurantCode": "cbk1",
"restaurantId": 159237,
"name": "Fast Pizza",
"url": "https://www.yemeksepeti.com/restaurant/cbk1/fast-pizza",
"cuisines": [
"Pizza"
],
"rating": 3.5,
"reviewCount": 501,
"reviewWithCommentCount": 0,
"priceLevel": 2,
"address": "camikebir mah. kasımpaşa mescid sok no11:b",
"city": "Istanbul",
"postCode": "X",
"latitude": 41.03621575,
"longitude": 28.96845685,
"distanceKm": 3.225,
"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 %20"
],
"openingHours": [
{
"weekday": 1,
"opens": "00:00",
"closes": "23:59"
},
{
"weekday": 2,
"opens": "00:00",
"closes": "23:59"
},
{
"weekday": 3,
"opens": "00:00",
"closes": "23:59"
},
"..."
],
"logoUrl": null,
"website": null
},
{
"rowType": "menuItem",
"restaurantCode": "cbk1",
"restaurantName": "Fast Pizza",
"menuName": "Ana Menü",
"categoryName": "Küçük Boy Pizzalar",
"productId": 56743924,
"productName": "Bol Malzemeli Pizza (Küçük Boy)",
"productDescription": "Sosis, domates, siyah zeytin, sucuk, yeşil biber, mantar, pizza sosu, mozzarella peyniri",
"variationId": 65007278,
"variationName": null,
"price": 336,
"priceBeforeDiscount": 420,
"discountPercent": 20,
"containerPrice": null,
"isSoldOut": false,
"isAlcoholic": false,
"isVegetarian": false,
"isPopular": true,
"imageUrl": "https://yemeksepeti.dhmedia.io/image/fd-tr/Products/56743924.jpg",
"optionGroups": null,
"currency": "TRY",
"scrapedAt": "2026-11-20T03:23:52.440Z"
}
]Input
| Field | Type | Required | Description | Default |
|---|---|---|---|---|
restaurantUrls | array | No | Restaurants to scrape directly, one per line. Paste restaurant URLs such as https://www.yemeksepeti.com/restaurant/awhi/eyup-sultan-sofrasi-awhi or bare codes such as awhi. Leave empty to discover restaurants from `locations` instead. An... | - |
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. Ignored when restaurant URLs or codes are given. Empty input ... | - |
mode | string | No | restaurants: one row per restaurant with rating, reviews, fees, minimum order, offers and hours. menus: that same restaurant row plus one row per menu item size (each orderable size is its own row) with TRY prices. | restaurants |
maxRestaurants | integer | No | Total number of restaurants to collect across all locations in discovery mode (1-3000). Restaurants are taken in the platform's listing order, so the cheapest runs are the smallest caps. When you pass restaurant URLs or codes, every entr... | 20 |
gridRadiusKm | integer | No | Optional square geo-grid around each location: 0 uses only the location point (one listing request per 50 restaurants). Set 3-10 to cover more of a city, with `gridStepKm` controlling the point spacing. Duplicates are removed by restaura... | 0 |
gridStepKm | integer | No | Spacing between grid points when `gridRadiusKm` is greater than 0 (1-10 km). Smaller steps cover a city more densely and cost more listing requests. | 3 |
searchQuery | string | No | Optional. Keep only restaurants whose name or cuisine contains this text, accent and case-insensitive (doner matches Döner). Applied to the listing in discovery mode. | - |
minRating | number | No | Optional. Keep only restaurants rated at least this (0-5), for example 4.5. Restaurants without a rating are dropped when this is set. | - |
maxMenuItemsPerRestaurant | integer | No | Menus mode only. Cap the number of menu item rows per restaurant (0 = the complete menu). Menu item rows are not billed per row, so 0 is fine for most runs. | 0 |
includeOptions | boolean | No | Menus mode only. Attach the option groups of each item (extras, dough, size choices...) with their prices to the item row as `optionGroups`. | false |
proxyConfiguration | object | No | Used only for restaurant detail and menu requests; restaurant discovery from a location needs no proxy. The default, Apify residential proxy in Turkey, is the tested setting: the menu API blocks repeated requests from one datacentre IP a... | {"useApifyProxy":true,"apifyProxyGroups":["RESIDENTIAL"],"apifyProxyCountry":"TR"} |
Example input
{
"locations": [
"Istanbul"
],
"proxyConfiguration": {
"useApifyProxy": true,
"apifyProxyGroups": [
"RESIDENTIAL"
],
"apifyProxyCountry": "TR"
}
}Pricing
| Event | What it means | Price | Lowest tier |
|---|---|---|---|
restaurant | One restaurant row delivered (rating, review counts, fees, minimum order, offers, hours, coordinates). Proxy and platform usage included. Error and info rows are never charged. | $0.0015 | $0.0012 |
restaurant-menu | One restaurant's complete menu delivered in menus mode (all item rows for that restaurant, any number of items). Charged once per restaurant. Proxy and platform usage included. | $0.001 | $0.0007 |
$1.50 at the listed price, or $1.20 on higher Apify plans, for 1,000 restaurants.
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 restaurants 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 restaurants (Free plan) | Higher plans (Gold) | Start fee per run | Platform usage | Users | Rating | Last build |
|---|---|---|---|---|---|---|---|
| Yemeksepeti Scraper: Restaurants, Menus & Prices This API | $1.50 | $1.20 | None | Included | 3 | No reviews yet | 20 Nov 2026 |
| Yemeksepeti Scraper — Restaurants, Menus & Prices | $3.00 | $1.50 | $0.00005 | Included | 22 | No reviews yet | 8 Nov 2026 |
| Yemeksepeti Scraper — Restaurants, Menus & Prices (Turkey) | $2.00 | $2.00 | $0.005 | Included | 3 | No reviews yet | 12 Nov 2026 |
| Yemeksepeti Scraper: Restaurants, Menus and Prices | $1.00 | $0.9 | $0.00005 | Included | 3 | No reviews yet | 16 Nov 2026 |
Where Yemeksepeti Scraper — Restaurants, Menus & Prices is stronger
Where Yemeksepeti Scraper — Restaurants, Menus & Prices is stronger
- Menu items come with the restaurant for no extra event
- Geo grid sweep with radius and step inputs covers a whole city
- Single billed event per vendor keeps a run easy to predict
Where this API is stronger
- Menus are a separate event, so a restaurants only run pays for restaurants alone
- Menu rows carry one line per item size with pre-discount price and option groups
- Filters include minimum rating, search text and direct restaurant URLs
Where Yemeksepeti Scraper — Restaurants, Menus & Prices (Turkey) is stronger
Where Yemeksepeti Scraper — Restaurants, Menus & Prices (Turkey) is stronger
- Output adds topic ratings, payment types and service fee fields
- Cuisine and sort filters plus an open now switch
- Option groups can be included with each menu item
Where this API is stronger
- Restaurants and menus are separate events, so a list run pays for restaurants only
- A radius and grid step sweep covers an area without listing delivery points
- Rows carry offers, opening hours and pickup or delivery flags
Where Yemeksepeti Scraper: Restaurants, Menus and Prices is stronger
Where Yemeksepeti Scraper: Restaurants, Menus and Prices is stronger
- Plain HTTP with concurrency and request rate controls
- Compact restaurant row with the core delivery fields
- Open status and delivery time range are returned per restaurant
Where this API is stronger
- Menu enrichment is priced per restaurant rather than per menu row
- Filters cover minimum rating, search text and restaurant URLs
- Rows add offers, opening hours, chain details and pickup flags
Only a handful of actors cover Yemeksepeti. hipersoft bundles menu items into the restaurant event, teodor_banea charges per row with a start fee, and dodoflix keeps a lean restaurant row with rate controls. Ours charges restaurants and menu enrichment as separate events, with one row per menu item size.
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
- Set locations to Istanbul, or paste restaurant codes such as awhi into restaurantUrls if you already know them.
- Set maxRestaurants, for example 20, and add searchQuery or minRating if you want to narrow the discovery.
- Choose mode restaurants for listings, or mode menus to get one row per orderable size.
- For menus, decide whether includeOptions should attach extras and size choices with their prices, and cap rows with maxMenuItemsPerRestaurant if needed.
- Leave proxyConfiguration on its default, which is what the menu requests need, then start the run in the Apify Console.
- Read restaurant rows and menuItem rows from the same dataset using rowType, then export as JSON, CSV or Excel.
cURL
curl -X POST "https://api.apify.com/v2/acts/subimpact~yemeksepeti-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"locations":["Istanbul"],"proxyConfiguration":{"useApifyProxy":true,"apifyProxyGroups":["RESIDENTIAL"],"apifyProxyCountry":"TR"}}'Python
from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("subimpact/yemeksepeti-scraper").call(run_input={"locations":["Istanbul"],"proxyConfiguration":{"useApifyProxy":true,"apifyProxyGroups":["RESIDENTIAL"],"apifyProxyCountry":"TR"}})
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-scraper').call({"locations":["Istanbul"],"proxyConfiguration":{"useApifyProxy":true,"apifyProxyGroups":["RESIDENTIAL"],"apifyProxyCountry":"TR"}});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);n8n
Use the Apify node (Run an Actor).
Actor ID: subimpact/yemeksepeti-scraper
Input JSON: paste the example input above.Limits
- Restaurant discovery from a location leaves detail-only fields such as address, opening hours, website and logo null.
- Menu requests need the residential proxy setting; direct menu requests may be blocked by the site's bot check.
- Menu item rows are capped only if you set maxMenuItemsPerRestaurant, and 0 means the whole menu.
- Prices and menus change at any time, so rows are a snapshot stamped with scrapedAt.
Questions people ask
What does a restaurant and a menu cost?
$1.50 per 1,000 restaurant rows and $1.00 per 1,000 menus, charged once per restaurant after its last menu item row. Menu item rows themselves are free, so a menu with 145 sizes costs the same as one with 10. Proxy traffic is included, and error or info rows are never charged.
Are prices in lira?
Yes. price, priceBeforeDiscount and containerPrice are in Turkish lira, and every row carries currency set to TRY as published at scrape time. No conversion is applied, so you keep the platform's own figure and handle any currency work yourself.
Do I need a login or a browser?
No. The Actor runs over plain HTTP with no browser, no login and no API key. Restaurant detail and menu requests go through the proxy configured in proxyConfiguration, because the menu endpoint sits behind a bot check that blocks repeated datacenter requests.
Why are address and opening hours empty in some rows?
Restaurants mode from a location uses listing data only, so detail-only fields such as address, openingHours, website and logo stay null to keep the run cheap. Scraping a specific restaurant by code or URL fetches its detail page and fills them in.
How many restaurants can one run return?
maxRestaurants takes 1 to 3000 in discovery mode, and gridRadiusKm with gridStepKm samples a square grid of points around a city to surface more of them. Duplicates are removed by restaurant code, and the run stops at the cap you set.
What happens when a restaurant fails?
Each restaurant gets its own proxy session, and a bot check is retried up to four more times with new sessions after 1, 2, 4 and 8 seconds. A restaurant that still fails becomes an uncharged error row and the run continues, so one bad page does not lose the batch.
Do I need the reviews actor too?
Only if you want review text. This Actor returns aggregate rating, reviewCount and reviewWithCommentCount; the separate Yemeksepeti Reviews actor returns review text, per-topic ratings, reviewer names and vendor replies for the same restaurants.
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.