/falabella/products/reviews/summary

POST /api/falabella/products/reviews/summary

Price: 1 credit

Get the aggregated review summary of a Falabella product by product id (or product URL): average rating, total review count, recommend counts, star distribution (1-5) and first/last review dates. Use the region field for cl/pe/co.

How to use it

Get the rating summary of a Falabella product by numeric product id (e.g. '153374617') or a product URL. Returns average_rating, review_count, recommended_count/not_recommended_count, rating_distribution (count per star 1-5), photo_count/video_count and first/last submission dates (unix seconds). Set region to cl, pe or co. Use the reviews endpoint for the individual review texts.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• region string — Falabella marketplace country: cl (Chile), pe (Peru), co (Colombia). (default: "cl"; one of: "cl", "pe", "co")
• product string required — Product id or a Falabella product URL. (examples: "153374617"; minLength: 1)

Response

• @type string (default: "FalabellaReviewSummary")
• product_id string required
• average_rating number nullable
• review_count integer nullable
• rating_range integer nullable
• recommended_count integer nullable
• not_recommended_count integer nullable
• photo_count integer nullable
• video_count integer nullable
• rating_distribution array (default: [])
  • @type string (default: "FalabellaRatingBucket")
  • rating integer nullable
  • count integer (default: 0)
• first_submission_at integer nullable
• last_submission_at integer 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 has no reviews or does not exist in this region 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.