Zalando Scraper API
A Zalando scraper API that searches the Zalando.it catalogue by keyword and returns one row per product: brand, name, current price, the EU-Omnibus reference prices — the 30-day median and the 30-day low, each with its own discount percentage — the article SKU, the packshot image and the product URL. Missing reference prices are null, never guessed.
$0.001 per delivered product · $2 free every month · Failed runs never billed
$ curl $QD/zalando_search/run \
-H "Authorization: Bearer $QD_API_KEY" \
-d '{"query": "scarpe", "max_results": 24}'
{ "status": "done", "count": 24,
"results": [
{
"sku": "…",
"brand": "…",
"name": "…",
"price": … } ],
"cost": 0.024 }
# 24 products × $0.001 · nothing delivered, nothing charged
Try it
Zalando product search, running now
Change the input and run it against the live collector — nothing to install, no sign-up.
Run it from your own code, on your own inputs
Same collector, same rows — $2 of free API credit every month, no card.
What a Zalando scraper API does
Zalando publishes no structured data on a catalogue page — no schema.org block, no hydration payload, and its old public catalogue endpoint answers 410 Gone — so this is one of the few collectors that reads server-rendered markup, and it does so without touching a single class name. Every class on the page is a hashed build artefact that changes when Zalando ships CSS. The parser reads the semantic skeleton instead, and its most durable anchor is an article element that contains a heading: the grid also renders influencer “outfit” tiles as articles, and they carry no heading, no price and no SKU, which is exactly what keeps them out of the rows.
Prices on Zalando are not a fixed shape. A card carries one, two or three price paragraphs and the count varies row to row — on a sampled page, 6 cards had one, 14 two and 4 three. Each row is therefore parsed by walking its own paragraphs and classifying each by content, never by index and never by zipping page-wide arrays, which would shift every row after the first single-price card. The two reference prices mean different things under the EU Omnibus rules and are delivered as two fields; a “da” (from) price is flagged price_from because its discount is an upper bound across variants.
Limits, in plain numbers
Everything that bounds one run of this collector. No hidden throttles.
Max per run
240 products
Price
$0.001 / product
Per 1,000
$1.00
Failed runs
Free zero rows, zero charge
Free every month
$2 no card
Rate limit
60 req/min on the free tier
What one product looks like
Every delivered product carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.
| Field | Type | What it holds |
|---|---|---|
rank | integer | 1-based position in this response. |
sku | string · nullable | Zalando article SKU, e.g. "AD116D1S8-A13" (config id + colour), read from the product URL. |
brand | string · nullable | Brand, e.g. "adidas Originals". |
name | string | Product name including type and colourway. |
price | number · nullable | Current price in EUR. When price_from is true this is the cheapest variant. |
price_text | string · nullable | Price exactly as the card shows it, e.g. "da 71,99 €". |
price_from | boolean | True for a "da" (from) price — the card spans variants priced differently. |
median_price | number · nullable | Zalando's stated 30-day median price ("Prezzo mediano"). An EU-Omnibus reference, NOT a list price. Null when the card states none. |
median_discount_percent | integer · nullable | Discount against median_price, as a positive percentage. |
lowest_price_30d | number · nullable | Zalando's stated lowest price of the last 30 days. Null when the card states none. |
lowest_price_30d_discount_percent | integer · nullable | Discount against lowest_price_30d, as a positive percentage. |
discount_is_max | boolean | True when the card says "Fino a" (up to) — the discount applies to the cheapest variant, not to every size. |
image | string · nullable | Packshot image URL. |
url | string · nullable | Product page URL. |
Inputs
The whole request. Anything you leave out falls back to the default shown in the catalog.
| Input | Type | Required | What it does |
|---|---|---|---|
query | string | yes | What to search on Zalando.it, e.g. "scarpe" or "nike air max". |
max_results | integer | no | How many products to deliver at most (1–240). You pay only for delivered products. |
Pricing
Zalando Scraper API pricing
$0.001 per delivered product. A run that delivers nothing costs nothing: blocked pages, challenges and retries are on us, and the $2 monthly allowance covers about 2,000 products before you spend anything.
Pay as you go
- $2 free credit / month
- 60 requests / min
- List unit prices
Starter
- $15 free credit / month
- 300 requests / min
- 10% off unit prices
Growth
- $50 free credit / month
- 600 requests / min
- 20% off unit prices
Scale
- $250 free credit / month
- 1,200 requests / min
- 30% off unit prices
Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — GET /v1/scraper/collectors returns the price your key actually pays.
Integration
One POST, typed rows
Base URL https://api.quanticdata.io/v1, Bearer auth, the same key as every other Data API. Endpoint: POST /v1/.
curl -X POST https://api.quanticdata.io/v1/scraper/collectors/zalando_search/run \
-H "Authorization: Bearer $QD_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"scarpe","max_results":24}'
What people build with the Zalando scraper API
Three shapes of work this endpoint was designed around.
Omnibus-compliant price monitoring
Current price against the 30-day median and the 30-day low, each with its own discount, so a “−40%” claim can be checked against what the rules require.
Brand and assortment tracking
Brand, name and SKU per product for a keyword, re-run weekly to see what entered, left or was repriced.
Cross-retailer comparison
Join by brand and product name with the ASOS and Nike rows to compare the same item across shops.
Zalando Scraper API versus rolling your own
The differences that actually cost time when you build this in-house.
| DIY scraper | This collector | |
|---|---|---|
| Selectors | Hashed class names that die on the next CSS deploy | Semantic structure only: an article with a heading |
| Outfit tiles | Parsed as products | Excluded by structure — no heading, no price, no SKU |
| Prices | Paragraph N of the card | Each paragraph classified by what it says |
| Reference prices | One “was” price, meaning unclear | Median and 30-day low as separate fields, null when absent |
What people search for
Live autocomplete demand around Zalando product search, pulled with our own Keyword ideas collector.
Sources and standards
The platform documentation and standards this collector is built against — check any claim on this page against the primary source:
Which Zalando country?
Zalando.it, priced in euro. The reference-price rules are the EU Omnibus ones, which is why the row carries both the 30-day median and the 30-day low.
What does price_from mean?
The card covers several variants and shows the cheapest as a “da” (from) price. Its discount is therefore an upper bound, and the row flags that with discount_is_max.
Why can a reference price be null?
Because Zalando does not state one for every product. A card may carry either reference price, both, or neither; the row reports what the card states and nothing more.
Will a Zalando redesign break it?
A restyle will not: no class names are read. A change to the page’s structure could, and the collector reports a zero-row page as a failure rather than a success, so it shows up in health rather than in your data.
Is there a free Zalando scraper API?
Every account gets $2 of credit every month with no card, which is about 2,000 delivered products on this endpoint at $0.001 each. It renews monthly, and a run that delivers nothing is never billed — so a failed or blocked attempt does not eat the allowance.
How much does one run cost?
Multiply the rows you actually receive by $0.001. A run capped at 240 products — the maximum for this collector — costs $0.24 if every row comes back, and less when the source has fewer. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the price your key actually pays.
Run the Zalando scraper API now
$2 of free credit every month, no card. Your key returns its own prices from GET /v1/scraper/collectors.