# /idealo/products/reviews

`POST /api/idealo/products/reviews`

Price: 10 credits

List the user reviews Idealo shows for one product on a chosen national Idealo site: the star rating, the review title and body, the author name, the date, which product variant the review refers to, whether the purchase was verified, and which review network the review came through.

## How to use it

Idealo unions two review sets here — its own, and Amazon/Otto reviews syndicated through Trustami — so `provider` tells you where a review came from and the sets can differ sharply in tone. A product with no reviews answers 200 with an empty list, and so does one Idealo lists but no shop currently sells; 412 means the chosen `country` site does not carry that id at all, which can be true on one site and false on another for the same product. An empty result is therefore an answer rather than a failure, and reviews concentrate on popular products, so a niche item usually has none. `reference` names the variant reviewed, which matters where one Idealo product covers several colours or capacities. For the aggregate instead of the individual reviews, `idealo/products/search` already carries `rating` and `review_count` per product. A list shorter than `count` is the whole set unless the response carries `X-Results-Truncated`, which says the source stopped answering part-way and the rest exists.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `product` (string, required) — Idealo product id or a product URL containing it (examples: "204743522", "https://www.idealo.de/preisvergleich/OffersOfProduct/204374464_-portasplit-3-5-kw-midea.html"; minLength: 1)
- `country` (string) — National Idealo site to read the reviews from. Each site shows the reviews written in its own language (default: "de"; one of: "de", "at", "gb", "fr", "it", "es")
- `count` (integer, required) — Max number of reviews to return (examples: 10, 50; min: 1; max: 300)

## Response

### 200 — Successful Response

- `@type` (string) (default: "IdealoProductReview")
- `id` (string, required) — Stable digest of the review's own content. Idealo publishes no review identifier, so this is derived from the product, author, date and text and is repeatable across calls
- `product_id` (string, required)
- `rating` (number, nullable) — Reviewer's rating on a 1-5 star scale, rounded to the nearest half star
- `review_title` (string, nullable)
- `text` (string, nullable)
- `author` (string, nullable)
- `date` (string, nullable) — Review date as YYYY-MM-DD
- `reference` (string, nullable) — The product variant the review was written about, as the review states it
- `is_verified` (boolean) (default: false)
- `provider` (string, nullable) — Which review network the review came through. Idealo's own reviews arrive via Cimenio; Amazon and Otto reviews arrive via Trustami

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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

This national Idealo site does not list a product with that id

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.