/n11/products/reviews

POST /api/n11/products/reviews

Price: 1 credit

Get customer reviews for an N11 product by product id (or product URL): rating, text, author, date, helpful count, seller and review photos. Supports sorting and filtering by star rating or topic.

How to use it

Fetch customer reviews for an N11 product by product id (numeric data-prod-id) or a product URL. Each review has id, rating (1-5), text (the review comment, in Turkish), author (masked), created_at (unix ms), created_date (dd/mm/yyyy), helpful_count, useless_count, seller_name and images. Use sort (RECENT, HELPFUL, FAVORABLE, CRITICAL), rating (1-5) and topic to filter. Returns up to `count` reviews.

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 id (data-prod-id) or a product URL (examples: "726304379", "https://www.n11.com/urun/apple-iphone-15-128-gb-apple-turkiye-garantili-43821353"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• sort string — Review sort order (default: "RECENT"; one of: "RECENT", "HELPFUL", "FAVORABLE", "CRITICAL")
• rating integer nullable — Filter reviews by star rating (min: 1; max: 5)
• topic string nullable — Filter reviews by topic tag

Response

• @type string (default: "N11ProductReview")
• id string required
• rating integer nullable
• text string nullable
• author string nullable
• created_at integer nullable
• created_date string nullable
• helpful_count integer nullable
• useless_count integer nullable
• seller_name string nullable
• images array (default: [])

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 — The entity was not found, or a precondition failed 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.