POST /api/mvideo/products
Price: 1 credit
Get one M.Video product by id or product URL: name, brand, category, description, final price, struck old price, discount percent, cashback bonus, promo badge, availability and prepayment flags, seller identity with INN and OGRN, marketplace offer counters, rating, review count, images and video, priced and stocked for the requested city.
The price returned is the public tier — a signed-in M.Video customer can be shown a lower one, so treat it as the walk-up price when comparing against other retailers. A null `price` means the id is not in M.Video's price feed for the requested city: the product record is still valid, it simply is not on sale there, and `status` and the bonus and discount fields go null with it. `is_new` is M.Video's new-arrival flag, not the item's condition — refurbished and markdown stock is marked by `used_product_type`. One product id belongs to one seller: `seller` is empty on M.Video's own stock and carries the company name, INN and OGRN on marketplace stock, so the same physical item from another seller lives under a different id. Spec tables and colour or storage variants are not available; for per-store stock and delivery dates call mvideo/products/stores with the same id and city.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)city string — M.Video city id the request is priced and stocked for. Store availability, pickup and delivery terms are resolved for this city, and the resolved city is echoed back in city_id / city_name. (default: "CityCZ_975"; examples: "CityCZ_975", "CityDE_31146", "CityCZ_36500"; minLength: 1)product string required — M.Video product id or a product page URL (examples: "30087002", "https://www.mvideo.ru/products/30087002"; minLength: 1)@type string (default: "MvideoProduct")id string requiredurl string requiredname string requiredalias string nullablemodel_name string nullablebrand string nullablebrand_id string nullablecategory_id string nullablecategory_name string nullabledescription string nullableprice number nullableold_price number nullablediscount_percent integer nullablebonus_amount integer nullablebadge string nullablestatus string nullablesold_out boolean (default: false)show_case boolean (default: false)available_only_in_retail_store boolean (default: false)is_prepayment boolean (default: false)is_cannot_be_exchanged boolean (default: false)is_preorder boolean (default: false)is_new boolean (default: false)is_last_chance boolean (default: false)seller_id string nullableseller string nullableseller_brand_name string nullableseller_inn string nullableseller_ogrn string nullableseller_address string nullableseller_phone string nullableseller_work_schedule string nullableis_main_offer boolean nullableother_offer_count integer nullablemain_offer_id string nullablemain_offer_alias string nullablematerial_source string nullableproduct_type string nullableused_product_type string nullablematerial_cis_number string nullableweight number nullablerating number nullablereview_count integer (default: 0)is_mprime_subscription boolean (default: false)sale_legal boolean nullablesublicense boolean nullableimage string nullableimages array (default: [])images_3d array (default: [])videos array (default: [])city_id string nullablecity_name string nullable422 — The input carries no M.Video product id, or the city id is unknown 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 product id in the M.Video catalogue 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.