Zalando Scraper

Pull product data from zalando.de, Europe's largest online fashion retailer. This scraper reads directly from Zalando's own server-rendered listings, so it returns clean, structured data — name, brand, price, sizes, stock, images — for real results, not a scraped screenshot of a page.

Two ways in: search keywords, or category page URLs pasted straight from your browser.

How to scrape Zalando data

Give the actor one or more search keywords (brand names, product types, or a mix — "adidas sneaker", "Damen Kleider", "Nike Sportswear" all work, German or English) and it runs them against Zalando's own /katalog/ catalog search, paging through results until it hits maxResults.

Or give it categoryUrls and it browses those category listings instead. Set both and it runs both, search first, into the same dataset.

Zalando sits behind Akamai's bot-management layer: a plain request to any zalando.de path, including robots.txt, gets a bare 403 at the edge — no JavaScript challenge is even served. This actor routes every request through Bright Data's Web Unlocker, which clears the block, so you don't need your own proxy or browser-automation setup.

Under the hood, Zalando server-renders its result grid directly into the page HTML as a window.__hydrationDataConsume(...) hydration blob — a GraphQL response cache with one full product object per card actually painted on the page (name, brand, price, available sizes, canonical product URL, image gallery). There's no separate hidden API call to reverse-engineer; the same Bright Data-fetched HTML page the actor already downloads for you IS the data source. Category pages carry the identical blob, so category results come back in exactly the same shape as search results. The actor pages through results with Zalando's own ?p= parameter, roughly 24 fresh products per page, and de-duplicates by SKU as it goes.

If you don't provide any input, it defaults to scraping Zalando's "Sneaker" search as a demo — a broad, cross-brand term with thousands of matches.

Scrape a whole category

Open the category you want on zalando.de, set any filters you like in the site's own interface, then copy the URL out of the address bar and paste it into categoryUrls. The actor pages through that listing until it runs out of products or hits maxResults.

{
  "categoryUrls": [
    "https://www.zalando.de/herrenbekleidung-jacken/",
    "https://www.zalando.de/damenbekleidung-kleider/"
  ],
  "maxResults": 500
}

Filters in the query string are kept and applied on every page. This returns leather jackets only:

{
  "categoryUrls": ["https://www.zalando.de/herrenbekleidung-jacken/?upper_material=leder"],
  "maxResults": 200
}

Details worth knowing:

• A page number in the URL (?p=3) is ignored — the actor drives pagination itself, from page 1.
• A bare slug works too: "damenbekleidung-kleider" is read as https://www.zalando.de/damenbekleidung-kleider/.
• Only zalando.de URLs are accepted. Anything else is skipped with a warning in the log.
• Zalando answers an unknown category slug with an HTTP 200 page that has no products on it. If a category returns nothing, open the URL in a browser first — the slug is usually the problem.
• maxResults is a single budget across every search query and every category in one run, and SKUs are de-duplicated across all of them, so the same product listed in two categories is returned once.
• fetchDetails works the same way in category mode as in search mode.

Input

Field	Type	Description
searchQueries	array of strings	Search keywords to run on zalando.de, e.g. "adidas sneaker". Up to 25 per run.
categoryUrls	array of strings	Category page URLs to browse, e.g. "https://www.zalando.de/herrenbekleidung-jacken/?upper_material=leder". Up to 25 per run. Runs alongside searchQueries when both are set.
maxResults	integer	Cap on number of products returned across all search queries and category URLs combined (default: 100)
brightDataApiKey	string	Your own Bright Data API key, if you want to use your own Web Unlocker zone instead of the actor's built-in one
proxyConfiguration	object	Not used — this actor reaches zalando.de exclusively through Bright Data, which handles unblocking on its own. Kept for input-shape compatibility.
fetchDetails	boolean	Off by default. Fetch each product's own page for material, care, fit and other specifications. See "Product detail mode" below.
maxDetailFetches	integer	Hard cap on detail-page fetches per run when fetchDetails is on (default: 500). Ignored when fetchDetails is off.

What you get back

Field	Type	Example
name	string	"SAMBA OG UNISEX - Sneaker low - footwear white/core black"
brand	string	"adidas Originals"
price	number	80.95
originalPrice	number | null	Pre-discount price, only present when Zalando marks a markdown
currency	string	"EUR" — zalando.de is a single-market, EUR-only storefront
sku	string | null	"AD116D1S8-A13"
productId	string | null	Same as sku
inStock	boolean | null	true when at least one size is purchasable, null only when the source doesn't confirm stock status — never coerced to false
url	string	Full product page URL
imageUrl	string | null	Primary product image
imageUrls	array	Up to 8 product images for the default color (video previews are filtered out)
category	string | null	Target group / silhouette label, e.g. "WOMEN / DRESS"
specs	object	Currently the available sizes, e.g. {"sizes": "38, 39 1/3, 40"}
attributes	object | null	Only present with fetchDetails on. Material, care, fit and other specs from the product page, keyed by cluster id.
material	string | null	Only present with fetchDetails on. Upper material, e.g. "Leder".
articleNumber	string | null	Only present with fetchDetails on. Zalando's own article number.
detailsFetched	boolean	Only present with fetchDetails on. True only when the detail page was fetched and parsed successfully.
detailUrl	string	Only present with fetchDetails on. The product page URL the detail fetch targeted.
scrapedAt	string	ISO timestamp

Product detail mode

By default this actor only reads the listing grid, which is enough for name, brand, price, sizes and images but doesn't carry material, care instructions or fit notes. Turn on fetchDetails in the input and the actor also opens each product's own page and pulls its full specification table. This works for both search queries and category URLs.

What it adds to each item:

• attributes — every spec row from the product page (material, care instructions, fit, sustainability, and anything else Zalando lists), keyed by the site's own section id, with the German field names as they appear on zalando.de
• material, articleNumber — the two most commonly used fields pulled out on their own for convenience
• detailsFetched and detailUrl — whether the detail fetch worked, and which page it targeted

It's off by default and costs one extra Bright Data request per product, on top of the listing requests — roughly one extra request per product for name/brand/price plus one for attributes. At Bright Data's Web Unlocker rate that's about $0.0015–0.003 per product, so a 100-product run with fetchDetails on makes about 100 extra requests. Use maxDetailFetches to cap that regardless of maxResults, so a large run can't accidentally trigger thousands of detail fetches.

Each product detail page fetched is charged as a separate event, product-detail-fetch, at $0.004.

Detail fetches run at low concurrency with a pacing delay between requests, so turning this on makes a run noticeably longer than a listing-only run of the same size. As with every run on this actor, usage cost only settles once the run reports SUCCEEDED — checking cost mid-run will undercount it.

Example input:

{
  "searchQueries": ["Nike Air Force 1"],
  "maxResults": 20,
  "fetchDetails": true,
  "maxDetailFetches": 20
}

Sample output

{
  "name": "SAMBA OG UNISEX - Sneaker low - footwear white/core black",
  "brand": "adidas Originals",
  "price": 80.95,
  "currency": "EUR",
  "url": "https://www.zalando.de/adidas-originals-samba-og-unisex-sneaker-low-footwear-whitecore-black-ad116d1s8-a13.html",
  "scrapedAt": "2026-09-04T14:13:39.915Z",
  "originalPrice": 89.95,
  "sku": "AD116D1S8-A13",
  "productId": "AD116D1S8-A13",
  "inStock": true,
  "imageUrl": "https://img01.ztat.net/article/spp-media-p1/34f7481205e141e3961668ccf6bfdbc7/137c32396c3845848ec5f3dda5582bc9.jpg?imwidth=500&filter=packshot",
  "imageUrls": [
    "https://img01.ztat.net/article/spp-media-p1/34f7481205e141e3961668ccf6bfdbc7/137c32396c3845848ec5f3dda5582bc9.jpg?imwidth=500&filter=packshot",
    "https://img01.ztat.net/article/spp-media-p1/e113bcc65f0f403e9fe53e230648d2ba/8e83ea24b37149a2bdeadf3c13e04b5a.jpg?imwidth=500"
  ],
  "category": "KIDS / SNEAKER",
  "specs": { "sizes": "35.5, 36, 36 2/3, 37 1/3, 38, 38 2/3" },
  "scrapedAt": "2026-09-04T14:13:39.915Z"
}

Use cases

• Price monitoring — track Zalando's own price and markdown changes over time on the brands and styles you sell against.
• Category sweeps — pull a whole category, filtered the way you'd filter it on the site, for a full picture of an assortment rather than a search-ranked slice of it.
• Assortment research — see which brands and products rank for a given search term on Europe's largest fashion marketplace.
• Market comparison — Zalando is the single biggest fashion retailer in Europe alongside Zara and H&M, making it a standard reference point when benchmarking fashion pricing.
• Stock and size tracking — inStock and the sizes spec flag when a product or a specific size run has sold through.

Coverage

zalando.de is Zalando's German storefront (EUR pricing, German-market catalog). Zalando runs separate country domains (zalando.fr, zalando.co.uk, zalando.it, ...) with distinct catalogs and currencies — this actor is scoped to zalando.de only.

Performance and cost

Every request goes through Bright Data's Web Unlocker, but a single listing page returns about 24 products in one call, for search results and category pages alike, so the Bright Data cost per result is a small fraction of a cent — well under a quarter of the per-result price, which is why this actor is priced at the standard e-commerce tier rather than a premium anti-bot tier. Category URLs cost exactly the same per result as search queries. A 100-product run typically completes in under a minute. Your run's usage cost only settles after the run reports SUCCEEDED — checking cost mid-run will undercount it.

Limitations

• Category URLs are taken as you paste them; the actor doesn't walk Zalando's category tree to discover sub-categories for you. List each category you want.
• originalPrice is only populated when Zalando marks an item as discounted; full-price items will show it as absent, which is correct, not missing data.
• Ratings and review counts aren't exposed on the search-result endpoint, so they're not included in the output.
• Per-size stock isn't included — sizes lists which sizes are currently purchasable, but not a count per size.
• If Zalando restructures its listing pages or hydration data shape, the actor will need updating — it depends on the exact structure of the window.__hydrationDataConsume(...) blob, for both the /katalog/ search page and category pages.
• Product detail mode (fetchDetails) depends on the product page's separate hydratePartial(...) fragment cache; if Zalando restructures that, attributes will need updating independently of the listing scraper.

Related scrapers

If you're covering European fashion more broadly, also check out:

• Zara Scraper — Inditex flagship, category-based catalog
• Mytheresa Scraper — luxury fashion e-tail, full per-size stock
• Vinted Scraper — European resale/secondhand fashion

Support

Found an issue or need a market that isn't resolving correctly? Open an issue on this actor's Apify Store page and we'll take a look.