/mvideo/products/stores

POST /api/mvideo/products/stores

Price: 10 credits

List the M.Video shop pickup points that can hand over one product in the requested city, with brand, handover type, address, metro, coordinates, opening hours, pickup date and per-store stock counts. Independent partner pickup-point networks (5post, Yandex, cdek and similar) are priced and counted upstream for the same product and city but their individual points are not covered here.

How to use it

Answers 'where can I collect this today' for one product in one city, covering M.Video's own shops only — independent partner pickup points (5post, Yandex, cdek and similar) can also hand the product over in the same city but are out of scope here, so an empty list means no M.Video shop can, not that nothing can. `stock_quantity` counts units on the shelf and is often 0 while `available_quantity` is 1 — the store can still hand the item over on `pickup_date` by moving it from a warehouse, so read the date rather than inferring from the counts. A store list is scoped to the city the request was priced for, so change `city` rather than expecting nationwide coverage. `city_id`/`city_name` echo the requested city; `store_city_id` is the store's own city and can be a suburb of the requested one. `brand` is the upstream chain field and reads 'MVIDEO' even for Eldorado-branded outlets — an Eldorado shop is identifiable by an 'EL:' prefix in `name`.

Parameters

• access-token string required

Request body

• timeout 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)
• count integer required — Max number of stores to return (min: 1)

Response

• @type string (default: "MvideoStore")
• id string required
• store_product_id string required
• product_id string required
• product_url string required
• name string nullable
• branch_name string nullable
• address string nullable
• metro string nullable
• metro_id string nullable
• latitude number nullable
• longitude number nullable
• working_schedule string nullable
• is_open_all_day boolean (default: false)
• pickup_time string nullable
• brand string nullable
• is_mmobile_shop boolean (default: false)
• handover_type string nullable
• pickup_date string nullable
• delivery_date_min string nullable
• stock_quantity integer nullable
• available_quantity integer nullable
• showcase_quantity integer nullable
• prepaid_quantity integer nullable
• prepaid_only boolean nullable
• store_city_id string nullable
• city_id string nullable
• city_name string nullable

Errors

• 422 — 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.

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.