M.Video Scraper: 39 Data Fields, Up to 1,000 Free Results/Month (2026)

Each record carries 39 output fields including current pricing in Russian rubles, technical specifications, and marketplace seller details. Coverage spans 89 curated categories alongside targeted search queries and direct URL lookups. At $5.00 per 1,000 results on the free-plan price, teams can monitor retail inventory and pricing without heavy spending. It is not for engineers needing multi-currency payouts or data from other stores like Citilink, as output prices are strictly native to the Russian market.

Try it: open M.Video Scraper on Apify, sign in on the free plan and run the prefilled example.

Can you try M.Video Scraper before paying?

Yes. Apify's free plan includes $5.00 of prepaid usage every month and asks for no credit card. At $0.005 per result, that covers up to 1,000 results of M.Video Scraper a month, before run-start charges and platform usage.

M.Video Scraper was last updated on 2026-07-24. It is one of 1,724 Actors CrawlerBros publishes on Apify, which together have 710,197 lifetime public runs and an average rating of 4.63 out of 5 across 416 reviews.

What does it cost to run M.Video Scraper?

Each result costs $0.005 on Apify's free plan, which is $5.00 per 1,000 results. Starting a run is charged separately at $0.005 per GB of Actor memory. Apify also bills the platform usage each run consumes, at the rates of your Apify plan, on top of these charges.

The maxItems control is the primary driver of total execution charges because it directly caps the dataset size. Setting server-side filters like brands or categoryUrl in byCategory mode lowers cost by preventing unwanted records from writing to the output dataset. To evaluate output fields without consuming budget, start with maxItems set to a low number.

How do you run M.Video Scraper from the API?

The schema marks 1 of its 15 controls as required: mode. The payload below uses the schema's own prefilled values, so it runs as written once you substitute your API token.

Call the synchronous endpoint to start a run and receive dataset items in one request:

curl -X POST "https://api.apify.com/v2/acts/crawlerbros~mvideo-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","category":"1","productUrls":["https://www.mvideo.ru/products/televizor-general-electronics-ge55lqs2-401211841"]}'

The same run from Python, using the official client:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")

run_input = {
  "mode": "search",
  "category": "1",
  "productUrls": [
    "https://www.mvideo.ru/products/televizor-general-electronics-ge55lqs2-401211841"
  ]
}

run = client.actor("crawlerbros~mvideo-scraper").call(run_input=run_input)

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

And from Node.js:

import { ApifyClient } from 'apify-client'

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' })

const input = {
  "mode": "search",
  "category": "1",
  "productUrls": [
    "https://www.mvideo.ru/products/televizor-general-electronics-ge55lqs2-401211841"
  ]
}

const run = await client.actor('crawlerbros~mvideo-scraper').call(input)
const { items } = await client.dataset(run.defaultDatasetId).listItems()
console.log(items)

The synchronous endpoint holds the connection open until the run finishes, which is convenient for small batches and wrong for large ones. For anything long running, start the run asynchronously and poll, or attach a webhook, so a dropped connection does not cost you the results.

Which M.Video Scraper inputs matter, and which can you skip?

The mode parameter is the single required input, selecting between keyword search, category browsing, or direct product URL extraction. For broad category sweeps, set category or supply a custom categoryUrl slug. Most users should leave proxyConfiguration at its default setting on initial execution.

• mode (string): What to fetch. Default: "search".
• category (string): Top-level mvideo.ru category to browse. Default: "".
• productUrls (array): mvideo.ru product URLs (e.g. https://www.mvideo.ru/products/televizor-...-401211841) or bare numeric product IDs. Default: [].
• searchQuery (string): Free-text product search, e.g. телевизор, ноутбук, холодильник. Default: "телевизор".
• categoryUrl (string): Overrides category. Accepts a full mvideo.ru category URL (e.g. https://www.mvideo.ru/televizory-i-cifrovoe-tv-1/televizory-65) or a bare numeric category ID, for sub-categories not in the dropdown.
• sortOrder (string): Result ordering for category browsing. Default: "popularity".
• brands (array): Only return products from these brands, server-side (AND with category). Use the brand's mvideo.ru filter slug - for Latin-script brands this is just the lowercase name (e.g. samsung, lg, sony, xiaomi, general-electronics); look up the exact slug by opening the category on mvideo.ru and checking the brand filter checkboxes if unsure. Multiple values are OR'd together. Default: [].
• sellers (array): Only return products from these marketplace sellers, server-side (AND with category). Use the seller's mvideo.ru filter slug (e.g. mvideo for M.Video itself, mediamarkt for MediaMarkt); look up the exact slug from the category's own seller filter if unsure. Multiple values are OR'd together. Default: [].
• minPrice (integer): Drop products cheaper than this (sale price, in Russian rubles). In mode=byCategory this is applied server-side (fewer wasted fetches); other modes filter client-side after fetching.
• maxPrice (integer): Drop products more expensive than this (sale price, in Russian rubles). In mode=byCategory this is applied server-side (fewer wasted fetches); other modes filter client-side after fetching.
• minRating (number): Drop products with a customer rating below this (0-5 stars). Products with no rating are excluded when this filter is set.
• inStockOnly (boolean): Only emit products that are currently available (not sold out). Default: false.

The other 3 controls, with their defaults, are listed in the input schema on M.Video Scraper on Apify.

Fixed-choice controls: mode accepts search (Search products by keyword), byCategory (Browse a category), productDetails (Fetch product details by URL/ID); category accepts 90 values (default ""), including 1 (Телевизоры и цифровое ТВ), "" ((none - required for byCategory)), 5 (Hi-Fi техника), 19 (PC игры и софт); sortOrder accepts popularity, priceAsc (Price: low to high), priceDesc (Price: high to low).

What does M.Video Scraper return?

Output datasets provide structured fields such as salePrice, discountPercent, and full technical specification tables. Detailed product records include up to 20 customer reviews alongside seller details like sellerInn and sellerOgrn. Note that historical price trends are not stored in a single record and require periodic scheduled runs.

• productId, name, modelName, brandName, brandId
• productUrl / sourceUrl
• categoryId, categoryName, breadcrumbs[], breadcrumbPath[] ({name, categoryId})
• salePrice, basePrice, discountPercent, currency (RUB), bonusAmount
• ratingStar, ratingCount, ratingBreakdown ({"1": count, ..., "5": count}), recommendPercent
• reviews[] ({reviewId, author, score, text, benefits, drawbacks, recommended, likes, dislikes, date, photoCount})
• inStock, storeOnly, isPreorder
• imageUrl, imageUrls[]
• description, specifications[] ({name, value} pairs)
• similarProducts[] ({productId, productUrl, differences[]}) - alternate SKUs in the same model line
• weightKg
• sellerId, sellerName, sellerLegalName, sellerInn, sellerOgrn, sellerPhone, sellerAddress
• recordType: "product", scrapedAt

These are the documented fields. Optional ones can be empty on a given record, so measure how often each field your deliverable depends on is populated across a real sample before automating the handoff.

How do you build the workflow end to end?

Open M.Video Scraper and work through these in order. Each step ends with something to check, so a bad configuration surfaces on a small run rather than a scheduled one.

1. Set mode to byCategory, search, or productDetails depending on whether you need category browsing, keyword search, or direct SKU lookups.
2. Select a category ID from category or supply a custom category URL in categoryUrl when running in byCategory mode.
3. Set maxItems to 10 on your first run to check record structures before triggering large dataset runs.
4. Inspect the emitted dataset to verify that salePrice, currency, and productId contain expected values.
5. Add lowercase brand filter slugs to the brands array to restrict category results server-side in byCategory mode.
6. Set maxReviews between 1 and 20 if your workflow needs review text, ratingBreakdown, or recommendPercent data.
7. Check availabilityStatus, inStock, and storeOnly fields in the returned dataset to ensure item inventory flags match your requirements.
8. Verify the scrapedAt timestamp on returned records to confirm data freshness before ingesting into downstream pipelines.

How do you apply it? Three worked playbooks

These are M.Video Scraper's own documented use cases, each worked through as an operating pattern rather than a description.

Use case 1: Price monitoring

Outcome: Track prices/discounts across a category over time

Configure: Set mode to "byCategory", category to "1", inStockOnly to true, and maxItems to 100.

Working method: Execute an initial baseline extraction across the category, then schedule daily runs using identical category settings to detect fluctuations in salePrice, basePrice, and discountPercent.

Deliverable: A structured dataset containing product IDs, timestamped sale prices, discount rates, and promotional badge text.

Stop condition: Stop the run if the dataset returns zero items or if salePrice is missing from records across consecutive pages.

Use case 2: Market research

Outcome: Compare brand assortment and pricing in Russian electronics retail

Configure: Set mode to "byCategory", categoryUrl to "https://www.mvideo.ru/televizory-i-cifrovoe-tv-1/televizory-65", brands to ["samsung", "lg", "xiaomi"], and maxItems to 200.

Working method: Execute separate runs across targeted brand facets, then aggregate the emitted datasets to evaluate comparative price spreads, availability ratios, and ratingStar distributions.

Deliverable: A multi-brand catalog extract detailing SKU counts, average selling prices, stock availability flags, and seller distribution across brands.

Stop condition: Stop the pipeline if the brands filter fails to narrow items and causes unrelated brands to populate the brandName field.

Use case 3: Product catalog enrichment

Outcome: Pull specifications and images for a known list of products

Configure: Set mode to "productDetails", productUrls to ["https://www.mvideo.ru/products/televizor-general-electronics-ge55lqs2-401211841"], and maxReviews to 5.

Working method: Provide an input array of existing internal catalog URLs or bare IDs, run the scraper, and map the returned specifications and imageUrls arrays directly into your product information management schema.

Deliverable: An enriched catalog record containing detailed attribute key-value pairs, multi-angle image URLs, customer reviews, and sibling SKUs via similarProducts.

Stop condition: Stop enrichment processing if product detail responses return empty specifications arrays for valid active URLs.

What breaks, and how do you design around it?

If search mode caps out at its limit of about 10 results, switch to byCategory mode with a specific category ID for complete category coverage. When brand filters do not return items, check mvideo.ru directly to verify you are passing the correct lowercase slug. For rich specification key-value arrays, use productDetails mode instead of broad category listing sweeps.

When should you not use M.Video Scraper?

Do not use this Actor if you require data across multiple Russian electronics chains in a unified schema. For other major electronics stores, use Citilink Scraper - Russian Electronics Store Products, Onlinetrade.ru Scraper, or Technopark.ru Scraper - Products, Categories & Search. For home appliances specifically, Holodilnik.ru Scraper provides specialized category coverage. This scraper is also unsuitable for real-time inventory polling requiring sub-second response times due to standard web scraping latency.

What should you check before trusting the output?

• Verify that salePrice is populated as a positive integer and that currency equals RUB for all returned items.
• Check that productId contains a non-empty string or numeric value for every written record.
• Ensure specifications is populated as an array of name and value objects when running in productDetails mode.
• Confirm that imageUrl contains a valid image URL string for catalog listings.
• Halt execution if more than 10 percent of records in a run return empty productId or name values.

None of this proves a record is correct. It gives a scheduled M.Video Scraper run defined points where it should stop instead of quietly passing bad data downstream.

Frequently asked questions

How much does it cost to scrape 1,000 products from M.Video?

Each result costs $0.005, which is $5.00 per 1,000 results on the free-plan price. Apify's free plan includes $5.00 of monthly usage without a credit card, covering up to 1,000 results of this Actor. Note that run-start fees and platform usage are billed separately.

Why does search mode only return 10 results?

The mode=search setting is capped at ~10 results because mvideo.ru's own search-suggestion API limits output to roughly 10 matches per query. For larger extractions, identify the category ID for your target items and switch to mode=byCategory, which supports full pagination up to 2,000 items.

Are filters like brand and price applied before I am charged?

In byCategory mode, filters for brands, sellers, minPrice, and maxPrice are applied server-side. The Actor only writes matching items to the dataset, preventing billing charges for non-matching records. In other modes, price and rating filters apply client-side after retrieval.

How do I fetch full specifications and customer reviews?

Set mode to search or productDetails to fetch full specifications arrays and customer reviews. High-level category sweeps in byCategory mode optimize for speed and emit listing details, omitting detailed spec tables and review text.

Where to go next

When you are ready to run it, open M.Video Scraper on Apify; the free plan covers up to 1,000 results a month.

Start with the M.Video Scraper Actor page for the current input schema, pricing tier, and run history.

Other Actors we maintain for related data:

• Citilink Scraper - Russian Electronics Store Products: Scrape Citilink.ru, one of Russia's largest electronics and appliance retailers.
• Onlinetrade.ru Scraper: Scrape onlinetrade.ru (Онлайн Трейд) - a major Moscow electronics and appliances retailer.
• Technopark.ru Scraper - Products, Categories & Search: Scrape Technopark.ru, a major Russian consumer-electronics retailer.
• Holodilnik.ru Scraper: Scrape Holodilnik.ru - a major Russian home-appliance retailer.
• Coolblue Scraper: Scrape Coolblue with the leading consumer electronics retailer in the Netherlands, Belgium and Germany.
• Petrovich Building Materials Scraper: Scrape Petrovich (petrovich.ru) - a major Russian building-materials and DIY retailer.
• Suning Scraper (China's electronics retailer): Scrape suning.com - one of China's largest electronics e-commerce platforms.
• X-Com Shop Scraper: Scrape XCOM-SHOP (xcom-shop.ru) - a major Russian electronics and computer retailer.

Related guides:

• ETM Electrical Equipment Scraper: 55 Data Fields per Record (2026)
• DNS-Shop Scraper: 25 Data Fields, Up to 1,000 Free Results/Month
• Megamarket.ru Scraper: Up to 1,000 Free Results a Month (2026)
• Ozon Scraper - Products, Categories & Search: 3 Practical Use Cases

Resources

• Actor documentation, input schema, and pricing: verified against the published Actor on 2026-09-30.

• Actor last updated by its maintainers on 2026-07-24.

• Run outcome figures cover the 30 day public window ending 2026-09-30.

• M.Video Scraper on Apify