/ozon/products/search

POST /api/ozon/products/search

Price: 20 credits

Search Ozon (ozon.ru) products by keyword: product cards with id, sku, title, url, images, price, original price, discount percent, rating, review count and the stock and promo badges, with price range, brand, seller, colour, fast-delivery, promotion, installment, brand-verified and discounted filters plus category-specific facets and result ordering.

How to use it

`price` is the price shown on the card for a buyer paying with an Ozon card, and `original_price` appears only where the seller struck one through, so its absence means no recorded discount rather than an unchanged price. Ozon publishes no result total, so a `count` larger than the keyword's own catalogue simply returns fewer rows. `brand`, `seller`, `color` and the `filters` facets take Ozon's numeric ids, and those ids are scoped to a category — read them from a previous search on the same keyword rather than assuming a global id space; a `filters` key the category does not offer is ignored rather than rejected, and the answer names it in `X-Warning`. `price_min`/`price_max` bound a price Ozon holds in its facet index rather than the `price` returned here, and rows near either edge do fall outside the requested range, so apply a hard cutoff on `price` yourself when the boundary matters. Prices and availability are quoted for the delivery region the request lands in, which is set by the exit and is not selectable, so treat figures as one Russian region's prices and not a national price. Use ozon/products for the specification table, description, stock quantity and seller of a single product. A keyword that resolves to one of Ozon's 18+ categories is served like any other.

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; max: 1000)
• sorting string — Result ordering (default: "popular"; one of: "popular", "newest", "price_asc", "price_desc", "high_rating", "big_discount")
• price_min integer nullable — Minimum price filter, RUB (min: 0)
• price_max integer nullable — Maximum price filter, RUB (min: 0)
• brand array nullable — Brand id filter (multiple allowed)
• seller array nullable — Seller id filter (multiple allowed)
• color array nullable — Color id filter (multiple allowed)
• fast_delivery boolean — Only products Ozon marks as fast delivery (default: false)
• is_promo boolean — Only products in the current promotion (default: false)
• is_installment boolean — Only products available in installments (default: false)
• original_only boolean — Only products whose brand Ozon has verified (default: false)
• discounted_only boolean — Only products sold below their original price (default: false)
• filters object nullable — Additional category-specific facets as key -> value(s), e.g. {'volumememoryphone': ['100956392'], 'smartphoneversion': '101030478'}. A key the category does not offer is ignored by Ozon and named in the X-Warning header
  • * union

Response

• @type string (default: "OzonProductSnippet")
• id string required
• sku integer nullable
• product_title string nullable
• url string nullable
• alias string nullable
• image string nullable
• images array (default: [])
• price number nullable
• original_price number nullable
• discount_percent number nullable
• currency string (default: "RUB")
• rating number nullable
• review_count integer nullable
• stock_text string nullable
• badge_text string nullable
• brand_logo string nullable
• is_adult boolean (default: false)

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 products found for this keyword and filter combination. 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.