POST /api/noon/sellers/reviews
Price: 1 credit
Get customer reviews about a Noon seller (marketplace partner) by partner code: reviewer name, rating, comment (with Arabic/English translation) and date. Filter by star ratings and sort by helpful or most recent.
List reviews about a Noon seller by partner code (e.g. p-99900) or a seller store URL. Returns reviews with id, display_name, rating (1-5), text (comment), text_translation, language and updated_at (unix seconds). Filter with ratings (list of stars) and sort (helpful or time).
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)region string — Marketplace region (drives currency, stock, pricing and localisation) (default: "uae"; one of: "uae", "saudi", "egypt", "kuwait", "bahrain", "oman", "qatar")language string — Content language (default: "en"; one of: "en", "ar")seller string required — Noon seller partner code or a seller store URL containing it (examples: "p-99900", "https://www.noon.com/uae-en/seller/p-99900/"; minLength: 1)count integer required — Max number of seller reviews to return (min: 1)ratings array — Keep only reviews with these star ratings (1-5) (default: [1,2,3,4,5]; examples: [5], [1,2])sort string — Review ordering (default: "time"; one of: "helpful", "time")@type string (default: "NoonSellerReview")id string requireddisplay_name string nullablerating integer nullabletext string nullabletext_translation string nullablelanguage string nullableupdated_at integer nullable422 — 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 partner code) 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.