/yandexmarket/products/search

POST /api/yandexmarket/products/search

Price: 20 credits

Search Yandex.Market products by keyword: product cards with id, title, image, displayed price, spec highlights, seller business id and sku, with price range, brand, seller, condition, payment, rating and ordering filters.

How to use it

Find products by keyword when you do not have an id. Results are one row per product carrying its cheapest current offer, and `product_id` is what /yandexmarket/products and /yandexmarket/products/offers accept — use those for the full card or the seller landscape. `price_with_card` is the price, and it is the one the card displays. There is deliberately no `price` field here: a listing page does not publish the seller's own base price, only the displayed one, so call /yandexmarket/products/offers when you need an unconditional per-seller figure to benchmark against another retailer. `price_min`/`price_max` filter on a third basis, so a result can land outside the requested range and `sort=price_asc` is not strictly monotonic; re-check the range client-side when it must hold. To narrow to one brand or one seller, run a first search and feed a `vendor_id` or `business_id` from a result row back in — there is no by-name form, and guessing an id returns an unrelated set rather than an error.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• text string required — Search keyword (examples: "iphone 15", "наушники"; minLength: 1)
• count integer required — Max number of results to return (min: 1)
• sort string — Result ordering (default: "dpop"; one of: "dpop", "aprice", "dprice", "rating", "date", "discount_p")
• price_min integer nullable — Minimum price filter (min: 0)
• price_max integer nullable — Maximum price filter (min: 0)
• condition string nullable — Product condition filter (one of: "new", "resale")
• payment string nullable — Accepted payment method filter (one of: "online", "card_courier", "cash_courier", "postpaid_pickup")
• high_rating boolean — Only highly-rated products (default: false)
• vendor_id integer nullable — Keep only products of one brand. Takes the vendor_id returned on a result row (examples: 29000150; min: 1)
• business_id integer nullable — Keep only offers from one seller. Takes the business_id returned on a result row (examples: 39036172; min: 1)

Response

• @type string (default: "YandexMarketSnippet")
• product_id string required
• sku_id string nullable
• offer_id string nullable
• business_id string nullable
• image string nullable
• alias string nullable
• currency string (default: "RUB")
• rating number nullable
• rating_count integer nullable
• vendor_id integer nullable
• category_ids array (default: [])
• specs_highlights array (default: [])
• price_with_card number nullable
• old_price number nullable
• discount_percent integer nullable
• condition string nullable
• available_count integer nullable
• delivery_text 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 — The search page itself did not come back, so nothing could be read — this is a delivery failure, not an empty result. A query that genuinely matches nothing returns 200 with an empty list instead, so do not retry a 412 by loosening filters; retry it as-is. 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.