POST /api/ozon/products
Price: 1 credit
Get one Ozon (ozon.ru) product by SKU or product URL: title, Ozon-card price, price without the card, struck-through original price and discount percent, availability and units in stock, rating and review count, brand and category path, gallery images and videos, the selling shop with its rating, lifetime order count and legal entity, the full specification table, the seller description with its images, package contents, colour and memory variants pointing at their own SKUs, and the number of competing seller offers.
The SKU is the only load-bearing part of an Ozon product URL, so a URL whose slug is stale or wrong still resolves as long as the trailing number is right, and a bare SKU is accepted. A seller id or a made-up number answers 412 rather than a wrong product. `price` is what a buyer paying with an Ozon card sees, `price_without_card` appears only when the two differ, and `original_price` only when the seller struck one through. `stock_quantity` is the units this one shop has left, not the product's total availability on Ozon — `other_offers_count` counts the competing shops, which ozon/products/offers lists with their prices. Prices, stock and `delivery_region` are quoted for the Russian region the request lands in, which is set by the exit and is not selectable. `characteristics` is the full spec table keyed by Ozon's own attribute keys (`VolumeMemoryPhone`, `Color`), and `aspects` gives the sibling SKUs for each colour or memory option, so read a variant's own SKU back into this endpoint rather than assuming its price matches.
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: "OzonProduct")id string requiredsku integer nullableproduct_title string nullableurl string nullablealias string nullableis_available boolean nullableprice number nullableprice_without_card number nullableoriginal_price number nullablediscount_percent number nullablecurrency string (default: "RUB")stock_quantity integer nullablemin_order_quantity integer nullablerating number nullablereview_count integer nullablebrand string nullablebrand_url string nullablecategory_id string nullablecategory_name string nullablecategory_path array (default: [])category_url string nullableimage string nullableimages array (default: [])videos array (default: [])seller object nullable@type string (default: "OzonProductSeller")id string nullablename string nullableurl string nullablerating number nullableorders_count string nullablelegal_name string nullablelegal_address string nullableother_offers_count integer nullableis_brand_certified boolean nullablemarketing_labels array (default: [])characteristics array (default: [])@type string (default: "OzonCharacteristic")key string nullablename string nullablevalues array (default: [])aspects array (default: [])@type string (default: "OzonAspect")key string nullablename string nullablevariants array (default: [])@type string (default: "OzonVariant")sku string nullableurl string nullablevalue string nullableprice number nullableoriginal_price number nullableimage string nullableavailability string nullabledescription string nullabledescription_images array (default: [])package_contents string nullabledelivery_region 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 such Ozon product: the SKU does not exist, or the id belongs to a seller rather than a product. 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.