# /yandexmarket/products/reviews

`POST /api/yandexmarket/products/reviews`

Price: 20 credits

Get Yandex.Market product reviews by id (or product URL): rating, text, pros, cons, author, date, photos and helpfulness votes.

## How to use it

Buyer reviews of one product card, by numeric id or product URL. Yandex groups sibling variants — the same item in another size or colour — under one card, so the feed can include reviews written for a sibling variant rather than the exact id you asked for; on an apparel listing most rows can be siblings. Each row's `product_id` is the id that review was written for, so compare it with the id you passed when that distinction matters to you. The feed is deliberately not narrowed to your id, because the grouping is the source's own and a shopper sees all of it. Rows arrive in the source's own ranking order: it is **not** chronological, and it rotates between calls, so two requests minutes apart return a different set of reviews in a different order. Position therefore means nothing — do not read the first row as the newest, and do not treat a given `count` as a stable slice you can page through. A review often carries only pros, only cons or only a comment, so read `pro`, `contra` and `text` together rather than expecting a single body. `created_at` is the Russian display date the site renders ('15 марта'), not a timestamp, and it omits the year for the current one, so it does not sort reliably either. `author` reads 'Имя скрыто' where the reviewer hid their name. Products with no reviews answer 412 rather than an empty list, and grey-market import listings routinely have none. A very long review feed is not served in full, so a large `count` can come back short of what you asked for.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `product` (string, required) — Yandex.Market product id or a full product URL (examples: "1082757784", "https://market.yandex.ru/product--x/1082757784"; minLength: 1)
- `count` (integer, required) — Max number of reviews to return (min: 1)

## Response

### 200 — Successful Response

- `@type` (string) (default: "YandexMarketReview")
- `id` (string, required)
- `product_id` (string, nullable)
- `author` (string, nullable)
- `author_id` (string, nullable)
- `author_avatar` (string, nullable)
- `rating` (integer, nullable)
- `text` (string, nullable)
- `pro` (string, nullable)
- `contra` (string, nullable)
- `created_at` (string, nullable)
- `images` (array) (default: [])
- `useful_count` (integer, nullable)
- `useless_count` (integer, nullable)

## 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

Product not found or has no reviews (well-formed id but no reviews available)

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.