/n11/products/sellers

POST /api/n11/products/sellers

Price: 10 credits

Get all sellers offering an N11 product by product id (or product URL) for price comparison: each seller with its id, name, rating, price, list_price, review count, whether it is the featured (winner) offer and free shipping.

How to use it

Fetch every seller offering the same N11 product (price comparison / buybox) by product id (numeric) or a product URL. Each item is one seller offer with seller_id, seller_name, rating (0-10 seller score), grade (0-100), price/list_price, review_count, is_winner (the featured offer shown by default), has_free_cargo, is_official_seller and url (link to that seller's offer).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — N11 product page id or a product URL containing it (examples: "43821353", "https://www.n11.com/urun/apple-iphone-15-128-gb-apple-turkiye-garantili-43821353"; minLength: 1)

Response

• @type string (default: "N11ProductSellerOffer")
• seller_id string required
• seller_name string nullable
• rating number nullable
• grade integer nullable
• price number nullable
• list_price number nullable
• review_count integer nullable
• is_winner boolean nullable
• has_free_cargo boolean nullable
• is_official_seller boolean nullable
• url 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 — Product not found (well-formed but nonexistent product id, 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.