# n11 Products & Price Scraper (Turkey) (`scrapyx/n11-products-scraper`) Actor

Scrape product listings from n11.com, a top Turkish marketplace. Every row carries both prices, the discount rate, seller name and official-seller flag, review counts, stock, shipping — plus n11's own rolling 7/10/14/30-day minimum price, so you get price history without repeated runs.

- **URL**: https://apify.com/scrapyx/n11-products-scraper.md
- **Developed by:** [Ibnu Adzim](https://apify.com/scrapyx) (community)
- **Categories:** E-commerce, Business, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.75 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## n11 Products & Price Scraper (Turkey)

Scrape product listings from **n11.com**, a top Turkish marketplace.

### What you get

One row per product (`recordType: PRODUCT`), from a 96-field upstream record:

| Group | Fields |
|---|---|
| Product | `productId`, `skuId`, `groupId`, `productTitle`, `productUrl`, `brandName`, `categoryName` |
| Price | `displayPriceValue`, `sellerPrice`, `oldPriceValue`, `discountRate`, `instantDiscountPrice`, `instantDiscountPercentage` |
| **Price history** | `firstMinFinalPriceForSevenDay` / `…TenDay` / `…FourteenDay` / `…ThirtyDay` — upstream's *own* rolling minimum price |
| Seller | `sellerId`, `sellerNickName`, `isOfficialSeller` |
| Reputation | `reviewCount`, `totalReviewCount`, `satisfiedScore`, `score` |
| Logistics | `stock`, `hasCriticalStock`, `isFreeShipping`, `hasSameDayDelivery`, `shipmentDeliveryType`, `isPreSale`, `isImport` |
| Ranking honesty | `isSponsored`, `searchRank`, `pageNumber` |

Plus the full upstream object spread in verbatim, a `SEARCH_SUMMARY` per
query, and an `ERROR` row per failed input — **every input maps to at least
one row**.

The rolling minimum-price fields are the unusual part: most marketplace
scrapers can only build price history by running repeatedly. n11 publishes
7/10/14/30-day minimums itself, so a single run already carries a month of
context.

### Example input

```json
{
  "searchQueries": ["laptop", "kulaklık"],
  "sortBy": "PRICE_LOW",
  "maxProductsPerQuery": 500,
  "includeSponsored": false
}
```

### Known limits — read before you buy

- **1,000 products per query, hard.** n11 clamps: request page 51 and you get
  **HTTP 200 with a full 20-row page whose `currentPage` is 1** — page one,
  re-served. Bisected exactly (page 50 honoured, page 51 clamped). Meanwhile
  the same response advertises `pageCount: 50,907` and `totalCount: 1,018,126`
  for `laptop`. Both numbers are real arithmetic and neither is reachable.
  The summary row carries `upstreamTotalCount`, `upstreamPageCountClaimed`,
  `reachableRowCeiling` and `pageClampReached` side by side so the gap is
  visible rather than implied.

  To cover more: narrow the query, or run the same query under a different
  `sortBy` — each ordering exposes a different 1,000-row slice.

- **Only four sort values do anything.** `PRICE_LOW`, `PRICE_HIGH`, `REVIEWS`
  and `NEWEST` measurably change the result set. `BEST_SELLER`, `SCORE` and
  `DEFAULT` return *byte-identical* first rows to no sort at all — n11
  silently ignores an unrecognised `srt` rather than rejecting it. Anything
  else is refused by this actor at input validation, because a typo would
  otherwise produce plausible, wrongly-sorted data.

- **No detail-page pass**, and that is a finding rather than an omission. The
  listing row already carries both prices, discount, seller, reviews, stock,
  shipping and the price history. A detail pass would double the requests to
  re-fetch what is in hand.

- **Sponsored placements are mixed into the ranking.** They are always flagged
  `isSponsored`; set `includeSponsored: false` to drop them for a clean
  organic ranking.

### How it works

No API key, no login, no browser. The listing arrives server-rendered in a
single `<script>window.model = {…}</script>` assignment (~273 KB) carrying
both the 96-field product records and honest pagination metadata.

The `schema.org/ItemList` JSON-LD on the same page was checked and **not**
used: it covers only 20 items with 4 fields each. This repo's usual stability
ladder puts JSON-LD first, and here it is simply worse — checked rather than
assumed.

### WAF and TLS

**None.** But one profile-shaped surprise worth knowing: `safari18_0` answers
**403** on the search surface while `chrome124`, `chrome131`, `chrome136`,
`chrome99_android` and `firefox133` all return the full 494 KB document. That
profile is excluded from the pool rather than left in to surface later as a
mystery failure.

Datacenter proxy pinned to Turkey is the default. The pin is a **correctness**
setting first: n11 serves prices, availability and promoted placements for the
local market.

### Policy

`n11.com/robots.txt` names no AI crawler, and `/arama` is allowed for
`User-agent: *`. Only public product listings are read — no login, no user
data, no personal profiles.

# Actor input Schema

## `searchQueries` (type: `array`):

Product keywords to search on n11.com, one per entry. Each query reaches at most 1,000 products — n11 silently re-serves page 1 past page 50, so several narrow queries beat one broad one.

## `sortBy` (type: `string`):

How results are ordered. Only values verified to actually change the result set are offered: n11 silently ignores an unrecognised sort and serves the default order, which would give you plausible but wrongly-sorted data. Changing the sort is also the practical way to reach a different 1,000-row slice of a large result set.

## `maxProductsPerQuery` (type: `integer`):

Stop after this many products per query. 1,000 is n11's hard ceiling: page 51 comes back as page 1 with a full 20 rows and HTTP 200, so nothing above that is reachable however you page.

## `includeSponsored` (type: `boolean`):

Keep promoted placements (n11's ad-bidding, power-ad and bold-ad slots). They are always flagged with 'isSponsored' either way. Turn this off for a clean organic ranking — mixing paid placements into a price-monitoring dataset without marking them is how ranking analyses go wrong.

## `maxConcurrency` (type: `integer`):

Upper bound on requests in flight across all queries. Paging inside one query is always sequential, because each page's stop condition depends on the previous response.

## `minRequestInterval` (type: `string`):

Minimum delay between the START of consecutive requests. This, not concurrency, is the honest speed control: once the rate cap binds, extra concurrency buys nothing.

## `proxyConfiguration` (type: `object`):

Proxy used for every request. Datacenter pinned to Turkey is the default — no bot mitigation was observed on any TLS profile, but n11 serves prices, availability and promoted placements for the local market, so a non-Turkish exit is a correctness risk before it is a blocking one.

## Actor input object example

```json
{
  "searchQueries": [
    "laptop"
  ],
  "sortBy": "",
  "maxProductsPerQuery": 100,
  "includeSponsored": true,
  "maxConcurrency": 3,
  "minRequestInterval": "0.6",
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `items` (type: `string`):

One row per scraped record. See the dataset's default view for field definitions.

# 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 = {
    "searchQueries": [
        "laptop"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapyx/n11-products-scraper").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 = { "searchQueries": ["laptop"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapyx/n11-products-scraper").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 '{
  "searchQueries": [
    "laptop"
  ]
}' |
apify call scrapyx/n11-products-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapyx/n11-products-scraper"
        }
    }
}

```

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/lrhp9PB9hCXeeT3Ws/builds/Y2tNl3V1J7S3uBRRO/openapi.json