/falabella/products/reviews

POST /api/falabella/products/reviews

Price: 5 credits

Get Falabella product reviews by product id (or product URL): rating, title, text, author, location, recommended flag, verified-purchaser badge, pros/cons, photos and submission date. Reviews are provided by Bazaarvoice and may be syndicated across HP/brand stores. Use the region field for cl/pe/co.

How to use it

Get user reviews of a Falabella product by numeric product id (e.g. '153374617') or a product URL. Returns rating (1-5), document_title, text, author, location, is_recommended, is_verified_purchaser, pros, cons, photos, positive_feedback_count, submitted_at (unix seconds), and syndication source when the review is syndicated from a brand store. Sort by most_recent, highest_rating, lowest_rating or most_helpful. Set region to cl, pe or co. Reviews with an empty list mean the product has no reviews.

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)
• count integer required — Max number of reviews to return (min: 1)
• sort string — Review ordering. (default: "most_recent"; one of: "most_recent", "highest_rating", "lowest_rating", "most_helpful")

Response

• @type string (default: "FalabellaReview")
• id string required
• rating integer nullable
• rating_range integer nullable
• document_title string nullable
• text string nullable
• author string nullable
• author_id string nullable
• location string nullable
• is_recommended boolean nullable
• is_verified_purchaser boolean (default: false)
• is_syndicated boolean (default: false)
• syndication_source string nullable
• syndication_url string nullable
• pros string nullable
• cons string nullable
• photos array (default: [])
• positive_feedback_count integer nullable
• source_client string nullable
• original_product_name string nullable
• content_locale string nullable
• submitted_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 — 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.