/leroymerlin/products/reviews

POST /api/leroymerlin/products/reviews

Price: 20 credits

Get customer reviews of a Leroy Merlin Italy or Spain product: rating, text, date, recommendation, verified-purchase flag and helpful votes

How to use it

Pass the product id from search results, or a product URL, with the country site it came from. A review with is_syndicated true comes from another Leroy Merlin site: its text is translated into the language of the site you asked, and original_text holds the wording as written. A review can carry a rating with no text.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• country string required — Leroy Merlin country site (one of: "it", "es")
• product string required — Leroy Merlin product id or product URL (examples: "89621591", "https://www.leroymerlin.it/prodotti/trapano-a-percussione-a-batteria-stanley-fatmax-br-1bt-18v-1-batteria-2ah-valigetta-89621591.html"; minLength: 1)
• count integer required — Max number of reviews to return (min: 1)
• sort string — Review ordering (default: "newest"; one of: "newest", "oldest", "highest_rating", "lowest_rating")
• rating integer nullable — Only reviews with this star rating (min: 1; max: 5)
• has_photos boolean — Only reviews with customer photos when true (default: false)

Response

• @type string (default: "LeroyMerlinReview")
• id string nullable
• product_id string nullable
• rating integer nullable
• text string nullable
• original_text string nullable
• syndication_source string nullable
• author string nullable
• author_level string nullable
• created_at integer nullable
• usage_duration string nullable
• helpful_count integer nullable
• unhelpful_count integer nullable
• is_recommended boolean nullable
• is_verified_purchase boolean nullable
• is_syndicated boolean nullable
• is_tester boolean 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 — No product has this id on that country site. 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.