en.zalando.de APIen.zalando.de ↗
Access Zalando's en.zalando.de catalog via API. Search products, browse categories, get product details, autocomplete suggestions, and list brands.
curl -X GET 'https://api.parse.bot/scraper/6fe2b064-20ba-45ea-af26-c8dc78f75a30/get_category_products?page=1&category_slug=womens-clothing' \ -H 'X-API-Key: $PARSE_API_KEY'
Scrape product listings from a category page on Zalando. Returns a paginated list of products with pricing, variants, and brand information.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| category_slugrequired | string | Category URL slug (e.g., 'womens-clothing', 'shoes', 'mens-clothing') |
{
"type": "object",
"fields": {
"page": "integer current page number",
"products": "array of product objects with product_id, sku, product_title, brand, price_eur, original_price_eur, currency, thumbnail_url, product_url, status, and variants",
"total_count": "integer total number of products returned on this page",
"brands_on_page": "array of unique brand name strings found on this page"
},
"sample": {
"data": {
"page": 1,
"products": [
{
"sku": "1FI81000E-A11",
"brand": "Fila",
"status": "Regular",
"currency": "EUR",
"variants": [
{
"sku": "1FI81000E-A110538000",
"size": "35-38",
"variant_id": "1FI81000E-A110538000"
}
],
"price_eur": 14.9,
"product_id": "1FI81000E-A11",
"product_url": "https://en.zalando.de/fila-invisible-plain-socks-unisex-6-pack-socks-white-1fi81000e-a11.html",
"product_title": "INVISIBLE PLAIN SOCK UNISEX 6 PACK - Socks - white",
"thumbnail_url": "https://img01.ztat.net/article/spp-media-p1/1998404d1992463f92f97acb28444e36/978c334eaad74b1498bf680725cfd47e.jpg?imwidth=300&filter=packshot",
"product_handle": "fila-invisible-plain-socks-unisex-6-pack-socks-white-1fi81000e-a11",
"original_price_eur": 14.9
}
],
"total_count": 107,
"brands_on_page": [
"Anna Field",
"Bershka",
"Fila"
]
},
"status": "success"
}
}About the en.zalando.de API
This API exposes 5 endpoints covering Zalando's English-language German storefront (en.zalando.de), returning product listings, detailed variant data, brand directories, and search autocomplete. The search_products endpoint accepts a keyword query and returns paginated results including price, SKU, brand, thumbnail URL, and per-product variant arrays. The get_product_detail endpoint resolves a single product URL to its full size variant list, current and original EUR prices, and color-inclusive product title.
Product Search and Category Browsing
The search_products endpoint takes a query string (e.g., 'nike shoes', 'red dress') and an optional page integer, returning an array of product objects. Each object includes product_id, sku, product_title, brand, price_eur, original_price_eur, currency, and thumbnail_url. The get_category_products endpoint works the same way but accepts a category_slug (e.g., 'womens-clothing', 'shoes') instead of a keyword, and additionally returns a brands_on_page array listing every unique brand name found in that page of results.
Product Detail and Variants
The get_product_detail endpoint accepts a full product URL or URL path and returns a richer record: all variants as an array of objects with variant_id, sku, and size; price_eur and original_price_eur for discount delta calculation; and product_title which includes the color variant name. This endpoint is the right choice when you need size-level availability data rather than the summary fields returned by search and category listings.
Brands and Autocomplete
The get_brands_list endpoint requires no inputs and returns the full catalog of brands available on Zalando, with each entry containing name, url, and internal id. The get_search_suggestions endpoint takes a partial query string (e.g., 'nik', 'adid') and returns a suggestions array of autocomplete phrase strings, which is useful for building typeahead interfaces or expanding keyword coverage for scraping pipelines.
Pagination and Currency
Both search_products and get_category_products return a page integer and total_count reflecting products on the current page (not a grand total across all pages). All price fields are denominated in EUR. The currency field in product objects confirms the denomination.
- Track price drops on specific Zalando products by polling
get_product_detailand comparingprice_euragainstoriginal_price_eur. - Build a brand-filtered product feed by combining
get_brands_listbrand IDs withsearch_productskeyword queries. - Monitor which brands appear in a category using the
brands_on_pagefield fromget_category_products. - Populate a typeahead search box with Zalando suggestions by calling
get_search_suggestionson partial user input. - Aggregate size availability across a product line by collecting
variantsarrays from multipleget_product_detailcalls. - Compare current vs. original EUR prices across a category page to identify discount patterns in a fashion segment.
- Index Zalando's brand directory for competitor or market research using the
name,url, andidfields fromget_brands_list.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Zalando have an official developer API?+
What does `get_category_products` return that `search_products` does not?+
get_category_products endpoint returns a brands_on_page array listing every unique brand name found in the current page of category results. The search_products endpoint does not include this field. Both return the same core product object structure including sku, price_eur, original_price_eur, thumbnail_url, and brand.Does the API return stock availability or inventory counts?+
get_product_detail endpoint returns size variants with variant_id, sku, and size, but does not include a stock count or in-stock boolean per size. You can fork this API on Parse and revise it to add an availability field if that data is present on the product page.Does `total_count` in search and category results reflect the full catalog count for a query?+
total_count field reflects the number of products returned on the current page, not the grand total across all pages. To estimate full result set size, you need to paginate through multiple pages using the page parameter.