Skip to content

MediaMarkt Product Pages, Scraped on Schedule

MediaMarkt product pages carry the signals most electronics teams need: price, sale price, stock state, SKU, brand, category, ratings, and image gallery.

OUTPUT FORMATSHTMLJSONMarkdown

This scraper API returns those fields from a MediaMarkt URL in one call, either as structured JSON or as rendered HTML for your own parser. It handles JavaScript rendering, proxy rotation, and country routing so the request stays a single function call rather than a browser fleet.

What a MediaMarkt product page returns

Each product page yields SKU, brand, price, sale price, stock state, warranty options, customer ratings, and the full image gallery. Category and product metadata come back alongside those fields, so a catalog sync does not need a second pass for taxonomy. The same call works across German and European markets when country routing is set.

Three workflows this API fits

Product-detail capture is the most common starting point: collect specifications and identifiers so inventory records and pricing decisions reflect what each listing actually states. Price tracking comes next, watching how competitor prices shift so adjustments respond to observed changes. Store-availability collection follows in-store stock so replenishment matches demand. All three share one request shape; only the target URLs and the fields you extract change.

Request controls and what each one changes

The API exposes a small set of controls that map directly to rendering, location, and output shape. Use the table below as a field/control map before writing extraction logic.

Choosing JSON, HTML, or Markdown

Structured JSON is the shortest path when downstream systems expect named fields. Rendered HTML is appropriate when your own parser already knows the page structure. Markdown output feeds LLM workflows without a separate conversion step. The choice is a pipeline decision, not a quality ranking: pick the format your next stage already consumes.

Worked example: one product page to a price field

Take a MediaMarkt product URL on mediamarkt.de. Send a GET request with your API key and set render_js=true so the page executes in a headless browser before parsing. Add extract_rules mapping a CSS selector to a field name such as price, or use ai_extract_rules with a natural-language description of the fields you want. The response returns parsed JSON, so the price value arrives as a named field rather than as HTML to search. If the page varies by country, add country_code to route through a residential IP in that country.

Two different limits: plan concurrency vs target throttling

The API applies concurrency limits per plan, not per-target rate limits. That distinction matters when a run slows down. If requests queue before reaching MediaMarkt, the constraint is your plan's concurrent request allowance. If MediaMarkt itself throttles aggressive patterns, spacing requests or using multiple sessions is the remedy. Diagnose which side is limiting before changing plan size.

How credits are consumed

Requests start at one credit each. JavaScript rendering adds cost: a successful request with JS rendering costs 5 credits. Premium proxies cost 10 credits without JS rendering or 25 with it. Stealth proxy requests cost 75 credits. Credits are valid for one month and do not roll over. Free-trial terms, the current plan table, and any additional credit-cost rules are set by the operator and should be confirmed against the live pricing page before a run is budgeted.

Setup path

Create an account to get an API key and free credits. Install an SDK for Python, Node.js, Go, PHP, Ruby, or Java, or use plain cURL. Send a GET request with a MediaMarkt URL. Add render_js, stealth_proxy, country_code, or ai_extract_rules only when the page requires them. Documentation and code samples cover each language.

Request controls and their effect
ControlWhat it doesCredit impact
render_jsRuns the page in a real headless browser and returns post-render HTML5 credits per successful request
country_codeRoutes through a residential IP in the specified countryCredit cost not specified in source
extract_rulesMaps CSS selectors to field names and returns parsed JSONCredit cost not specified in source
ai_extract_rulesNatural-language field specification returning parsed JSONCredit cost not specified in source
premium_proxyPremium proxy rotation10 credits without JS, 25 with JS
stealth_proxyStealth proxy for CAPTCHA-heavy targets75 credits

Credit figures are captured from the upstream source on its source date and are not independently verified by this page; they may change. The relationship between stealth_proxy and the 'Rotating & Premium Proxies' plan feature is unconfirmed in the source. Check current pricing before committing to a plan.

Frequently asked questions

How do I handle JavaScript when scraping MediaMarkt?

Pass render_js=true on the request. The page runs in a real headless browser, JavaScript executes server-side, and the response contains the post-render HTML.

Can I scrape MediaMarkt from a specific country?

Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when content varies by geography.

What's the rate limit for scraping MediaMarkt?

The API applies concurrency limits per plan rather than per-target rate limits. If the target throttles aggressive patterns, space out requests or use multiple sessions.

How do I get structured JSON from MediaMarkt?

Pass extract_rules with CSS selectors mapped to field names, or use ai_extract_rules with a natural-language specification. The response returns parsed JSON.

Which programming languages can I use to scrape MediaMarkt?

Any language works. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java. Plain cURL also works.

How much does it cost to scrape MediaMarkt?

Credit cost per request depends on options: 5 credits for JS rendering, 10 credits for premium_proxy without JS rendering or 25 with it, and 75 for stealth_proxy. Free-trial terms, the current plan table, and any additional credit-cost rules are set by the operator and should be confirmed against the live pricing page before a run is budgeted.