/n11/sellers

POST /api/n11/sellers

Price: 10 credits

Get an N11 seller (store) by alias or store URL: name, company_name, rating, product count, city, time on platform, response time, shipment speed, feedback count, store logo and cover image.

How to use it

Fetch a single N11 seller (marketplace store) by alias or a store URL (/magaza/{alias}). Returns one item with name, alias, company_name (legal entity), rating (0-10 seller score), grade (0-100), sell_item_count, city, time_in_platform, response_time, shipment_speed, feedback_count, tax_number, mersis_no, is_official, is_quick_seller, is_top_seller, image (store logo) and cover (store banner).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• seller string required — N11 seller alias or a store URL containing it (examples: "aksarayiletisim", "https://www.n11.com/magaza/aksarayiletisim"; minLength: 1)

Response

• @type string (default: "N11SellerStore")
• id string required
• name string nullable
• alias string nullable
• company_name string nullable
• url string nullable
• rating number nullable
• grade integer nullable
• sell_item_count integer nullable
• city string nullable
• time_in_platform string nullable
• response_time string nullable
• shipment_speed string nullable
• feedback_count integer nullable
• tax_number string nullable
• mersis_no string nullable
• is_official boolean nullable
• is_quick_seller boolean nullable
• is_top_seller boolean nullable
• image string nullable
• cover string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Seller not found (well-formed but nonexistent alias, or page has no seller data) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.