Zalando Product Listings via a Scraper
A managed scraping API is useful when you need Zalando product-level data but do not want to run your own headless browser fleet or proxy pool.
You send a Zalando URL; the service renders the page, rotates proxies and returns HTML or structured output that your pipeline can parse. This page explains the three common Zalando data jobs, the request controls that matter, and how credits are consumed.
What you can pull from Zalando
Zalando product pages are typically mined for three families of data. First, product details: SKU, brand, price, size variants, color options, ratings, customer reviews and the image gallery. Second, seasonal trend signals: new-arrival tags, sale percentages and category-level pricing shifts. Third, per-SKU review data: star ratings and review text.
A single product-page request can return product name, brand, price, sizes, colors, ratings and product image URL without you parsing HTML. The same request can also be configured to return rendered HTML, Markdown, plain text, a screenshot or AI-extracted JSON.
Three Zalando scraping patterns
Choose the pattern that matches the downstream decision. A catalog refresh needs stable product fields and size/color availability. A merchandising review needs sale percentages and new-arrival flags across categories. A quality or sentiment workflow needs review text and star ratings tied to a SKU.
All three patterns use the same request shape: a Zalando URL plus the controls that fit the page. The difference is in the parsing target and the refresh cadence, not in the transport.
Request control map
The controls below are the ones most relevant to Zalando pages. Use them as a checklist before you scale a job.
- render_js: set to true when the data appears only after client-side JavaScript runs. The service executes the page in a headless browser and returns post-render HTML.
- stealth_proxy: enable when a target responds aggressively to normal traffic. It is the escalation path after standard proxy rotation.
- country_code: route through a residential IP in a specific country when Zalando content varies by market.
- ai_extract_rules: send a natural-language extraction spec and receive structured JSON without writing selectors.
- Screenshots and CSS/XPath extraction rules: capture a full-page screenshot or target exact elements.
A practical order is: try the default request, add render_js if fields are missing, add country_code if the wrong market is returned, and add stealth_proxy only if the response indicates blocking.
How credits are consumed
Credits are consumed per successful request, and the cost depends on which features are enabled. The pricing module below preserves the full plan table and the feature tooltips. Read it as a cost model: a plain request starts at one credit, JavaScript rendering raises the per-request cost, and premium proxies raise it further depending on whether rendering is also on.
Prices and allowances are listed in the plan table below; check the current pricing page before you commit to a plan.
Blocked, throttled or missing JavaScript: three different failures
A failed Zalando job usually falls into one of three buckets, and each has a different fix.
- Blocked response. The page returns a challenge or an empty shell even though the URL is correct. Escalate to stealth_proxy and confirm that proxy rotation is active.
- Throttled response. The target starts rejecting or slowing requests after a burst. The API itself applies concurrency limits per plan rather than per-target rate limits, so space out requests or use multiple sessions if the target throttles aggressive patterns.
- Missing JavaScript-rendered fields. The HTML arrives but price, size or review blocks are absent. Set render_js=true and re-check the post-render HTML.
Separating these three cases prevents wasted credits on the wrong control.
Worked example: one product page, one structured record
Suppose you are refreshing a European fashion catalog. You send one Zalando product URL with render_js enabled. The response can include product name, brand, price, size variants, color options, ratings and product image URL. Your pipeline maps those fields into a catalog row keyed by SKU.
If the same page also needs review text, add a second request or an ai_extract_rules spec that names the review fields. Keep the SKU as the join key so catalog and review records stay aligned. For a market-specific view, add country_code and store the country alongside the record so later comparisons are not mixed.
Setup path
Create an account to get an API key and free test credits. Install the SDK for your stack or send a GET request with the target URL. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. Code samples are available in the major languages, and the documentation covers the advanced parameters.
Commercial terms
Commercial terms for this service are not yet published on this page. Use the following checklist to evaluate any plan before committing, and treat every item as unconfirmed until you have it in writing from the provider you are considering. Pricing: request the current per-plan price list, the credit allowance attached to each tier, and the concurrency ceiling, then compare them against your expected monthly request volume. Credit validity: ask whether unused credits expire at the end of each billing period or roll over, and how partial or failed requests are counted. Cancellation: confirm the notice period, whether cancellation takes effect immediately or at the end of the term, and whether any refund applies. Free trial allowance: establish how many test credits are offered, whether a payment method is required to start, and what happens when the trial balance runs out. Support: clarify which channels are available on each tier, the expected response window, and whether priority handling is included or sold separately. Tax: check whether quoted prices include or exclude VAT and any other applicable taxes for your billing country. Enterprise arrangements: if your volume exceeds the published tiers, ask for a custom quote covering credits, concurrency and account management. Data protection: request the provider's written statement on personal data handling, including whether scraped personal data is stored, for how long, and how GDPR or CCPA obligations are addressed. References: ask for named customer references or case studies you can contact directly rather than relying on marketing quotes. Usage figures and ratings: request the methodology behind any customer-count or satisfaction figures so you can judge whether they apply to your use case. Awards and certifications: ask for the issuing body and date of any award or compliance certificate before treating it as evidence. Record each answer in writing so the comparison between providers rests on verified terms rather than assumptions.
| Plan | Price | API Credits | Concurrent requests | JavaScript rendering | Rotating & Premium Proxies | Geotargeting | Screenshots & Extraction Rules | Priority Email Support | Dedicated Account Manager | Team Management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
Prices exclude VAT. Credit validity, rollover and per-request costs are shown in the feature tooltips. Check the current pricing page before you commit to a plan.
| Feature | Credit cost |
|---|---|
| Plain request | 1 credit |
| JavaScript rendering enabled | 5 credits |
| Premium proxies, JS rendering disabled | 10 credits |
| Premium proxies, JS rendering enabled | 25 credits |
Credit costs are per successful request and match the feature tooltips. Check current rates before you budget a large job.
Frequently asked questions
How do I start scraping Zalando?
Create an account, copy your API key and send a GET request with the Zalando URL. The service renders the page, rotates proxies and returns the data. Free test credits are available so you can validate the response before scaling.
Will I get blocked when scraping Zalando?
Standard requests rotate residential proxies and use a real headless browser, so traffic resembles normal browsing. If a target responds aggressively, enable stealth_proxy on the request as an escalation step.
Can I scrape Zalando without writing code?
Yes. The dashboard request builder lets you paste a URL, set parameters and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL. You can also drive the API from no-code tools such as n8n.
How do I handle JavaScript when scraping Zalando?
Set render_js=true on the request. The page runs in a headless browser, JavaScript executes server-side and you receive the post-render HTML.
Can I scrape Zalando from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when Zalando content or availability differs by market.
What's the rate limit for scraping Zalando?
The API applies concurrency limits per plan rather than per-target rate limits. If Zalando throttles aggressive request patterns, space out requests or use multiple sessions.
Which fields should I join on across catalog and review jobs?
Use the SKU as the join key. Product-page responses can include SKU, brand, price, size variants, color options, ratings and review text, so a SKU-keyed record keeps catalog and review data aligned when you refresh them on different schedules.
Should I enable stealth_proxy for every Zalando request?
No. Start with the default request and add stealth_proxy only when a response indicates blocking. Enabling it by default raises the per-request credit cost and can mask a simpler configuration problem such as a missing render_js flag.