POST /api/ozon/products/offers
Price: 1 credit
List every Ozon (ozon.ru) shop selling the same product as the given SKU: each shop's own SKU for the item, its name, storefront URL and logo, its rating and review count, the Ozon-card price it charges, the registered legal entities behind it and whether the brand has authorised it, ordered cheapest first.
This is the price comparison across shops for one item, so it answers 'who else sells this and for how much'. A row's `id` and `sku` are that shop's own listing, not the SKU asked for — that is the id to pass to ozon/products for its stock and specification. The SKU you pass is not among the rows: these are the competing listings only. `price` is the Ozon-card price and is quoted for the Russian region the request lands in, which is set by the exit and is not selectable. The answer is the complete set of competing shops rather than a sample, so its length matches `other_offers_count` from ozon/products. `legal_entities` names the registered company behind the shop, which is how a grey-import reseller is told from an authorised one alongside `is_authorized_seller`.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)product string required — Ozon product SKU, or any ozon.ru product URL containing it (examples: "2795954097", "https://www.ozon.ru/product/apple-smartfon-iphone-15-2795954097/"; minLength: 1)@type string (default: "OzonSellerOffer")id string requiredsku integer nullableurl string nullableseller_id string nullableseller_name string nullableseller_url string nullableseller_logo string nullablerating number nullablereview_count integer nullableprice number nullableoriginal_price number nullablediscount_percent number nullablecurrency string (default: "RUB")product_image string nullablelegal_entities array (default: [])is_authorized_seller boolean nullableauthorized_seller_text string nullable422 — The input carries no Ozon product SKU. 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 competing offers for this product, or the SKU does not exist. 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.