/yandexmarket/products

POST /api/yandexmarket/products

Price: 20 credits

Get full Yandex.Market product details by id (or product URL): title, brand, image, description, price, rating, review count, category breadcrumbs, primary seller and spec table.

How to use it

One full product card, by bare numeric id or by any Yandex.Market product, card or offers URL. The card describes whichever offer is cheapest at that moment, so almost every field can differ between two calls minutes apart — even `brand`, which reads 'Без бренда' when a no-name reseller is currently cheapest. Only the catalog identity holds still, so re-fetching is not a way to confirm a product and a changed brand is not a different product. **`price` is the Yandex-card price of whichever offer was cheapest when the card was read — the same quantity the listing endpoints publish as `price_with_card`, not the pre-card base price /yandexmarket/products/offers calls `price`** — so comparing it against that `price` column is always wrong. Even against `price_with_card` the two endpoints can disagree, because each samples the offer pool independently and that pool rotates between calls. `rating` and the review counts are null on listings with no review page, which is normal rather than an error. `category_id` comes back in one of two forms, depending on how the source built that product's breadcrumb: an all-digits catalog id, which /yandexmarket/categories/products accepts directly, or an SEO slug such as 'mobilnyye-telefony-apple', which it rejects with 422. Both are common. So test whether `category_id` is numeric before passing it on, and treat the slug form as a label rather than a key.

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: "1912483624", "https://market.yandex.ru/product--smartfon-apple-iphone-15/1912483624"; minLength: 1)

Response

• @type string (default: "YandexMarketProduct")
• id string required
• url string required
• brand string nullable
• image string nullable
• description string nullable
• price number nullable
• currency string (default: "RUB")
• rating number nullable
• review_count integer nullable
• rating_count integer nullable
• category string nullable
• category_id string nullable
• hid integer nullable
• nid integer nullable
• vendor_id integer nullable
• seller_name string nullable
• seller_rating number nullable
• seller_rating_count integer nullable
• breadcrumbs array (default: [])
  • @type string (default: "YandexMarketBreadcrumb")
  • name string required
  • category_id string nullable
• specs object (default: {})
  • * string

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 not found (well-formed id but the product does not exist on Yandex.Market) 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.