/mvideo/products/search

POST /api/mvideo/products/search

Price: 5 credits

Search M.Video products by keyword. Returns id, url, name, final price, struck old price, discount percent, cashback bonus, promo badge, availability status, rating, review count and images, priced and stocked for the requested city.

How to use it

Keyword entry point into the M.Video catalogue. A bare product id also works as the query and resolves to that one product. Facet ids differ between search and category listings — take the ids for `filters` from a search response for the same query, not from mvideo/categories/products. Prices are the public tier; a signed-in M.Video customer can see a lower one.

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)
• count integer required — Max number of products to return (min: 1)
• sort string — Result ordering (default: "popularity"; one of: "popularity", "price_asc", "price_desc")
• price_min integer nullable — Lowest final price in roubles to keep (examples: 20000; min: 0)
• price_max integer nullable — Highest final price in roubles to keep (examples: 120000; min: 0)
• filters array — Any other facet M.Video exposes for this category or query, passed as its own id and option ids. A facet id that this category or query does not expose is rejected with 422 instead of being ignored. (default: [])
  • id string required — Facet id exactly as M.Video returns it for this category or query (examples: "cvet", "vstroennaya-pamyat", "tsvet-89"; minLength: 1)
  • values array required — Facet option ids to keep. A price-style range facet takes one 'min-max' string. (examples: ["chernyi","belyi"], ["50000-120000"]; minItems: 1)
• query string required — Search keyword (examples: "iphone 17", "холодильник", "диван угловой", "30087002"; minLength: 1)

Response

• @type string (default: "MvideoProductCard")
• id string required
• url string required
• name string required
• price number nullable
• old_price number nullable
• discount_percent integer nullable
• bonus_amount integer nullable
• badge string nullable
• status string nullable
• sold_out boolean (default: false)
• is_new boolean (default: false)
• is_original boolean nullable
• is_preorder boolean (default: false)
• is_last_chance boolean (default: false)
• rating number nullable
• review_count integer (default: 0)
• image string nullable
• images array (default: [])
• city_id string nullable
• city_name string nullable

Errors

• 422 — A facet id or option in filters is not exposed for this query, 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 — The entity was not found, or a precondition failed 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.