/ceneo/products/reviews

POST /api/ceneo/products/reviews

Price: 20 credits

List buyer reviews of one Ceneo product: author, star rating, recommend flag, verified-purchase flag, review text, the tagged pros and cons, when it was written and since when the buyer had been using the product, helpful and unhelpful vote counts, comment count, and - when the review was written about a sibling model rather than this exact one - the product it came from.

How to use it

Ceneo pools reviews across the colours and capacities of one model, so a large share of what comes back was written about a sibling product: check `is_from_similar_product` before attributing a complaint to the exact id you asked for. `stars` is one bucket, not a minimum, and caps the answer at a single page - drop it and use `sort` when you want depth. `created_at` and `used_since` are unix seconds; `used_since` is when the buyer started using the product, so the gap between the two is how long they had it before writing.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Ceneo product: a numeric product id or any ceneo.pl product URL (examples: "157123293", "https://www.ceneo.pl/157123293"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• sort string — Order the reviews are listed in (default: "usefulness"; one of: "usefulness", "newest", "oldest", "rating_desc", "rating_asc")
• stars integer nullable — Keep only reviews in this whole-star bucket, which also covers the half star below it (4 covers 3.5 and 4.0). Ceneo serves a single page of these, so at most 10 come back (min: 1; max: 5)

Response

• @type string (default: "CeneoReview")
• id string required
• product_id string required
• url string nullable
• author string nullable
• rating number nullable
• rating_max number nullable
• is_recommended boolean nullable
• is_verified_purchase boolean (default: false)
• text string nullable
• pros array (default: [])
• cons array (default: [])
• created_at integer nullable
• used_since integer nullable
• helpful_vote_count integer nullable
• unhelpful_vote_count integer nullable
• comment_count integer nullable
• source_product_id string nullable
• source_product_name string nullable
• is_from_similar_product boolean (default: false)

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 — No Ceneo product with that id. 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.