# Zalando Catalogue by Category (`ikmal_suzali_atr/zalando-catalog`) Actor

Every product on a Zalando category listing (Germany (zalando.de), United Kingdom (zalando.co.uk), France (zalando.fr), Italy (zalando.it), Spain (zalando.es), Netherlands (zalando.nl), Poland (zalando.pl)): id, name, brand, price, original price, rating, seller and sponsored flag, page by page,…

- **URL**: https://apify.com/ikmal\_suzali\_atr/zalando-catalog.md
- **Developed by:** [AtTheRate AI](https://apify.com/ikmal_suzali_atr) (community)
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Zalando Catalogue by Category

Pulls every product on a Zalando category listing across seven European storefronts (Germany, United Kingdom, France, Italy, Spain, Netherlands and Poland), one row per product with brand, price, size availability, promotional flags and a sponsored marker. Built for fashion brands and retail analysts who need the complete shelf of a category in its real order.

### What you get

- Complete coverage page by page, with `category`, `category_title`, `breadcrumbs`, `page` and `position` on every row.
- Brand-first data: `brand` is populated, making brand share a direct count.
- Price with the discount split out: `price` is the live selling price, `original_price` the crossed-out price when the article is reduced, and `currency` follows the storefront (EUR, GBP or PLN).
- `sizes`, the sizes still buyable on the card, plus `in_stock`, so you see depth of availability and not just presence.
- `flags`, Zalando's merchandising labels such as "Deal" or "Bestseller", as shown to the shopper.
- `is_sponsored` per row, read from the advertising marker Zalando attaches to a slot in its own collection data.
- `expandSubcategories` walks the children from Zalando's navigation tree and stamps each row with `parent_category`.

### Input

Give it category paths or Zalando URLs and a storefront.

```json
{
  "categories": ["/damenschuhe-sneaker/"],
  "locale": "de",
  "maxPages": 1,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"],
    "apifyProxyCountry": "DE"
  },
  "expandSubcategories": false,
  "delayMs": 1200,
  "callsPerSession": 60
}
```

- `categories` (required): paths such as `/damenschuhe-sneaker/` or URLs such as `https://www.zalando.de/herren-schuhe/`.
- `locale`: `de`, `uk`, `fr`, `it`, `es`, `nl` or `pl`. Default `de`.
- `maxPages`: pages per category. `0` means every page Zalando reports.
- `expandSubcategories`: also crawl the children from Zalando's navigation tree.
- `proxyConfiguration`: residential in the storefront's country, already the default.

### Output

One dataset row per product, in listing order.

```json
{
  "platform": "zalando",
  "locale": "de",
  "category": "/damenschuhe-sneaker/",
  "page": 1,
  "position": 1,
  "id": "BEJ11A0X9-A11",
  "name": "Sneaker low - white",
  "brand": "Bershka",
  "price": 20.99,
  "original_price": 29.99,
  "currency": "EUR",
  "in_stock": true,
  "is_sponsored": false,
  "sizes": ["35", "36", "37", "38", "39", "40", "41"],
  "flags": ["Deal"],
  "condition": null,
  "product_url": "https://www.zalando.de/bershka-sneaker-low-white-bej11a0x9-a11.html",
  "fetched_at": "2026-09-12T03:00:13.642Z"
}
```

Zalando shows no star ratings on category cards, so `rating` and `rating_count` are null. `condition` is null for new articles, and `category_title` with `breadcrumbs` are null on paths where the site publishes no tree.

### Use cases

- Brand share inside a category: group `brand` over `position` to see who owns the visible shelf.
- Discount monitoring from `price` against `original_price`, with `flags` showing when Zalando itself calls it a deal.
- Size availability: a shrinking `sizes` array between runs is an early stock-out signal.
- Assortment gaps across seven markets, and ad placement share from `is_sponsored` paired with `position`.

### Notes and limits

- A verified run on `/damenschuhe-sneaker/` at `zalando.de` returned 66 products from page one. Page size varies by category and storefront.
- Sponsored placements are not in every category. Both verified runs reported zero sponsored rows, so `is_sponsored: true` is a real signal rather than an expected one.
- Search paths are not categories. A `/katalog/?q=...` path is rejected and counted in `failed_categories`.
- A few cards can arrive without their detail payload. Those rows keep `id` and `is_sponsored` and are marked with `card_missing`.
- Prices are normalised to numbers in the storefront's currency, PLN on `pl` and GBP on `uk` included.

### FAQ

**Do I need a proxy?** Yes. Residential in the storefront's country (DE, GB, FR, IT, ES, NL or PL), already the default.

**How many results can I get?** `maxPages: 0` walks every page Zalando reports. One verified page returned 66 products.

**Does it need a login or an API key?** No. No Zalando account and no API key.

**How are subcategories found?** From Zalando's public navigation tree for the chosen storefront, so children match the site's own menu rather than a guess from page links.

# Actor input Schema

## `categories` (type: `array`):

Zalando category paths or URLs, e.g. "/damenschuhe-sneaker/" or "https://www.zalando.de/herren-schuhe/". Enable "Include subcategories" to crawl the children from Zalando's navigation tree.

## `locale` (type: `string`):

Which storefront / locale.

## `maxPages` (type: `integer`):

0 = all pages.

## `expandSubcategories` (type: `boolean`):

Also crawl each category's subcategories when the site exposes them.

## `delayMs` (type: `integer`):

Pause between page fetches.

## `callsPerSession` (type: `integer`):

Re-mint the session after this many page fetches.

## `proxyConfiguration` (type: `object`):

On the Apify platform this decides egress. A residential proxy in the storefront's country is recommended (DE for the default). On our own servers it is ignored and our residential proxy is used.

## Actor input object example

```json
{
  "categories": [
    "/damenschuhe-sneaker/"
  ],
  "locale": "de",
  "maxPages": 0,
  "expandSubcategories": false,
  "delayMs": 1200,
  "callsPerSession": 60,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "DE"
  }
}
```

# Actor output Schema

## `results` (type: `string`):

One row per product.

## `summary` (type: `string`):

Counts for the run: what was requested, captured, skipped and failed.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "categories": [
        "/damenschuhe-sneaker/"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ikmal_suzali_atr/zalando-catalog").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "categories": ["/damenschuhe-sneaker/"] }

# Run the Actor and wait for it to finish
run = client.actor("ikmal_suzali_atr/zalando-catalog").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "categories": [
    "/damenschuhe-sneaker/"
  ]
}' |
apify call ikmal_suzali_atr/zalando-catalog --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ikmal_suzali_atr/zalando-catalog"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/7tHughwWnqyvkqVwC/builds/7WwfuddGeRYlE4k38/openapi.json