/yandexmarket/products/offers

POST /api/yandexmarket/products/offers

Price: 20 credits

Get the seller offers listed for a Yandex.Market product by id (or product URL): per-offer price, price with card, old price and discount, condition, delivery estimate, stock and seller details.

How to use it

Competing seller offers for one product — this is where Yandex.Market prices actually differ, so compare sellers here instead of re-reading /yandexmarket/products, whose single price is just the cheapest offer of the moment. Yandex serves at most 16 offers per product and a popular product has far more, so treat the result as the leading offers rather than the whole market and do not read the count as a seller count. This is the only surface with a per-seller `price`; the listing endpoints publish only the displayed price. `price` is what the seller charges and `price_with_card` is the lower headline conditional on a Yandex card, so quote `price` when benchmarking another retailer and `price_with_card` when reproducing what a shopper sees. **Check `is_personal_price` before treating any of them as a public price** — Yandex personalises offers, and a personalised figure is not what another visitor is quoted. `old_price` is a marketing anchor, often far above anything recently charged; `previous_price` is the real prior price where the source states one. A null delivery flag means the page rendered no delivery options for that offer, not that the option is unavailable.

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)
• count integer required — Max number of offers to return (min: 1)

Response

• @type string (default: "YandexMarketOffer")
• product_id string required
• sku_id string nullable
• offer_id string nullable
• business_id string nullable
• shop_name string nullable
• shop_alias string nullable
• shop_rating number nullable
• shop_rating_count integer nullable
• alias string nullable
• image string nullable
• price number nullable
• price_with_card number nullable
• old_price number nullable
• discount_percent integer nullable
• previous_price number nullable
• previous_discount_percent integer nullable
• is_personal_price boolean nullable
• currency string (default: "RUB")
• condition string nullable
• available_count integer nullable
• delivery_text string nullable
• in_stock boolean nullable
• has_pickup boolean nullable
• has_courier boolean nullable
• vendor_id integer nullable
• category_ids array (default: [])
• is_super_price boolean nullable
• vat string 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 offers found (well-formed id but the product does not exist or has no sellers) 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.