# Zara Scraper (`datascrapers/zara-scraper`) Actor

Zara product data from category URLs and search terms, with storefront, filters, and sort options. Optional size, composition, and description details. Structured JSON per product.

- **URL**: https://apify.com/datascrapers/zara-scraper.md
- **Developed by:** [Farhan Ali](https://apify.com/datascrapers) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.20 / 1,000 product scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

**Zara Scraper** creates a structured dataset of Zara.com products collected from category pages, search terms, or individual product URLs. Each dataset item represents one product and includes its name, price, currency, colour variants, images, and URL; when enabled, it also attaches description, composition, colours, sizes, and per-size availability. Query the source using `startUrls`, `searchQueries` (with a `storefront`), or both, filter with the same controls shoppers use on the site, cap the result with `maxItems`, and retrieve records through the Apify Dataset API or export them as JSON, CSV, Excel, XML, or another supported format.

### Dataset at a glance

| Property | Value |
|---|---|
| Source | Zara.com |
| Record unit | One product |
| Input methods | `startUrls`, `searchQueries` (+ `storefront`, `section`) |
| Main identifiers | `productId`, `reference`, `url` |
| Delivery | Apify Dataset and API |
| Export formats | JSON, CSV, Excel, HTML, XML |
| Update model | Fresh records per Actor run |
| Pricing | Pay-per-event: $1.50 / 1,000 products; optional details billed at the same rate |

### Coverage and available records

The Actor accepts two seed types, processed in the same run (URLs first, then search terms):

- **Category or product URLs** (`startUrls`) — the country/language in the path selects the store and its currency (for example `de/en` for Germany/English/EUR, `us/en` for USD, `uk/en` for GBP).
- **Search queries** (`searchQueries`) — resolved against the `storefront` field (default `de/en`) and optionally restricted to a `section` (`ALL`, `MAN`, `WOMAN`, `KID`, `HOME`).

Grid filtering mirrors the site:

- `filters` accepts `color` and `size` (on-site labels, e.g. `Black`, `36`), `priceMin`/`priceMax` in the store currency, plus additional Zara filter ids as extra keys.
- `sort` maps to the site control: `default` (Featured), `price-asc`, `price-desc`, or `novelty`.

Conditional enrichment is controlled by `includeProductDetails` (default `false`). When enabled, each product is enriched with a `details` object (description, composition, colours, sizes, SKUs, per-size availability) using parallel requests governed by `detailConcurrency` (1–20). `maxItems` caps the combined total across all sources (`0` = unlimited).

### Data dictionary

| Field | Type | Nullable | Description | Example |
|---|---:|---|---|---|
| `imageUrl` | string | Yes | Primary product image URL | `"https://static.zara.net/..."` |
| `images` | array | Yes | Gallery image URLs | `["https://static.zara.net/..."]` |
| `name` | string | No | Product title | `"SLIM FIT JEANS"` |
| `price` | number | No | Store price in the market currency | `49.95` |
| `currency` | string | No | Currency code from the store | `"EUR"` |
| `availability` | string | Yes | Stock status on the listing | `"IN_STOCK"` |
| `color` | string | Yes | Selected colour label | `"Black"` |
| `colors` | array | Yes | Colour variants (with hex codes) | `["Black", "Blue"]` |
| `section` | string | Yes | Department the product belongs to | `"MAN"` |
| `url` | string | No | Canonical product page URL | `"https://www.zara.com/de/en/..."` |
| `sourceQuery` | string | Yes | Search term that produced the row | `"shorts"` |
| `sourceUrl` | string | Yes | Category/search URL that produced the row | `"https://www.zara.com/de/en/man-jeans-l659.html"` |
| `productId` | number | Yes | Zara product identifier | `2432131` |
| `reference` | string | Yes | Internal reference code | `"1234/456"` |
| `displayReference` | string | Yes | Customer-facing reference | `"1234/456"` |
| `family` | string | Yes | Product family grouping | `"JEANS"` |
| `subfamily` | string | Yes | Product subfamily grouping | `"SKINNY"` |
| `tags` | array | Yes | Product tags | `["new", "sale"]` |
| `categoryId` | number | Yes | Category id when scraped from a grid | `123456` |
| `details` | object | Yes | Product details; present only when `includeProductDetails` is on | see below |

The optional `details` object carries `description`, `composition`, `colors`, `sizes`, `skus`, and per-size `availability`. The best stable field for deduplication is `productId`, with `url` as a fallback.

### Example dataset record

The following representative record was produced from a category URL with `includeProductDetails` enabled. Identifiers are illustrative.

```json
{
  "imageUrl": "https://static.zara.net/photos/.../1/w/563/1234.jpg",
  "images": ["https://static.zara.net/photos/.../1/w/563/1234.jpg"],
  "name": "SLIM FIT JEANS",
  "price": 49.95,
  "currency": "EUR",
  "availability": "IN_STOCK",
  "color": "Black",
  "colors": ["Black", "Dark Blue"],
  "section": "MAN",
  "url": "https://www.zara.com/de/en/slim-fit-jeans-p01234567.html",
  "sourceQuery": null,
  "sourceUrl": "https://www.zara.com/de/en/man-jeans-l659.html",
  "productId": 2432131,
  "reference": "1234/456",
  "displayReference": "1234/456",
  "family": "JEANS",
  "subfamily": "SKINNY",
  "tags": ["jeans", "denim"],
  "categoryId": 659,
  "details": {
    "description": "Slim-fit jeans with five pockets and a faded wash.",
    "composition": "98% cotton, 2% elastane",
    "colors": ["Black", "Dark Blue"],
    "sizes": ["32", "34", "36", "38"],
    "skus": ["P01234567-32", "P01234567-34"]
  }
}
```

### Query and input reference

| Input | Type | Required | Default | Accepted values | Description |
|---|---:|---|---|---|---|
| `startUrls` | array | No\* | — | category/product URLs | Zara category or product URLs; country/language in the path sets the store. |
| `searchQueries` | array | No\* | `["shorts"]` | free text | Product search terms, resolved against `storefront`. |
| `storefront` | string | No | `de/en` | `de/en`, `us/en`, `uk/en`, … | Market for search queries (country/language). |
| `section` | string | No | `ALL` | `ALL`, `MAN`, `WOMAN`, `KID`, `HOME` | Department for search queries. |
| `filters` | object | No | `{}` | `color`, `size`, `priceMin`, `priceMax`, extra keys | Same filters as the Zara grid. |
| `sort` | string | No | `default` | `default`, `price-asc`, `price-desc`, `novelty` | Sort order. |
| `includeProductDetails` | boolean | No | `false` | `true` / `false` | Fetch description, composition, colours, sizes. |
| `detailConcurrency` | integer | No | `8` | `1`–`20` | Parallel detail requests when details are on. |
| `maxItems` | integer | No | `0` | `0` = unlimited | Maximum products across all sources. |
| `proxyConfiguration` | object | No | Apify `RESIDENTIAL` | proxy config | Proxy settings; residential recommended. |

\*Provide at least one of `startUrls` or `searchQueries`. A minimal request and an advanced request:

```json
{ "startUrls": [{ "url": "https://www.zara.com/de/en/man-jeans-l659.html" }], "maxItems": 20 }
```

```json
{
  "searchQueries": ["shorts"],
  "storefront": "de/en",
  "section": "MAN",
  "filters": { "color": ["Black"], "size": ["36"], "priceMin": 20, "priceMax": 80 },
  "sort": "price-asc",
  "includeProductDetails": true,
  "detailConcurrency": 8,
  "maxItems": 50,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}
```

### Retrieve the data through the API

1. Start the Actor with a JSON input.
2. Wait for the run to finish, or use the synchronous `?waitForFinish=` endpoint when appropriate.
3. Read items from the run's default dataset.
4. Paginate or export the dataset.

A Python example using the Apify client:

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("datascrapers/zara-scraper").call(
    run_input={"searchQueries": ["shorts"], "storefront": "de/en", "maxItems": 20}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["name"], item["price"], item["currency"])
```

For other languages, use the generated API tab on the Actor page. Never place a real token in a URL or example.

### Data quality and record handling

- **Conditional fields** — `details` is present only when `includeProductDetails` is on; product URLs may include details without a second fetch. `sourceQuery` and `sourceUrl` reflect the seed that produced the row.
- **Completeness** — listing-only rows omit description, composition, sizes, and SKUs.
- **Deduplication** — each run outputs one row per `productId` discovered in that run; re-runs can repeat the same product. Deduplicate across runs on `productId` or `url`.
- **Retries** — detail requests run in parallel and each uses a fresh proxy; individual products fail soft so one failed detail does not stop the run.
- **Normalization** — `price` is numeric; `currency` follows the storefront. Source field names are preserved in camelCase.
- **Raw versus derived** — all fields are source values; the Actor does not derive or convert currencies.

### Export and pipeline examples

| Destination | Recommended method | Typical use |
|---|---|---|
| PostgreSQL / Supabase | Dataset API or webhook consumer | Price history and catalog storage |
| Google Sheets | Apify integration | Assortment snapshots for merchandising |
| S3 / cloud storage | Scheduled export or integration | Daily catalog archives |
| PIM / marketplace feed | Scheduled run + export | Keep listings aligned with Zara's catalog |

### Pricing and cost examples

Billing is pay-per-event. Each product written to the dataset triggers the `product` event; when `includeProductDetails` is on, a row that includes a `details` object also triggers `product-details`.

| Event | What counts | Rate (per 1,000) |
|---|---|---|
| `product` | Each product saved to the dataset | $1.50 |
| `product-details` | Each product with a `details` object | $1.50 |

Higher Apify plan tiers apply a discount (per 1,000): Bronze $1.40 / Silver $1.30 / Gold $1.20. A one-time Actor Start event ($0.00005) is also applied per run. For this Actor's pay-per-event model, platform usage is not billed separately to the end user beyond the event rates above.

| Records | Estimated base cost |
|---:|---:|
| 1,000 products (listing only) | $1.50 |
| 10,000 products (listing only) | $15.00 |
| 1,000 products with details | $3.00 |

Estimates assume the standard tier; detail-enabled runs pay the `product` and `product-details` events per row that includes details.

### Limitations and responsible data use

- The Actor collects publicly accessible Zara.com product data only.
- Product availability and pricing reflect the storefront at crawl time and can change.
- Some fields are conditional or empty (see Data quality).
- No historical snapshots are guaranteed unless you store the exported datasets yourself.
- You are responsible for complying with applicable privacy, contractual, and legal requirements when using the data.

### Dataset questions

#### What does one dataset item represent?

One Zara product, optionally enriched with a `details` object (description, composition, colours, sizes, SKUs) when `includeProductDetails` is enabled.

#### Which field should I use as a unique identifier?

Use `productId`; fall back to `url` or `reference` when `productId` is absent.

#### Which currency appears in the output?

The store's currency. Category and product URLs use the country/language in the path; `searchQueries` use the `storefront` field (default `de/en`, EUR). Switch to `us/en` for USD or `uk/en` for GBP.

#### Can I combine category URLs and search queries?

Yes. `startUrls` are processed first, then `searchQueries`. `maxItems` applies to the combined total.

#### What counts as a billable result?

Each product is a `product` charge. A row that includes a `details` object (details on) also triggers `product-details`.

#### Are fields nullable or conditional?

Yes. `details`, `sourceQuery`, `sourceUrl`, `color`, and several identifier fields are conditional on the seed type and whether details are enabled.

### Related datasets from Data Scrapers

- **Nike Scraper** — Nike.com product records; adjacent apparel catalog data for brand comparison.
- **Amazon Scraper** — Amazon product, price, and seller data for marketplace research.
- **eBay Scraper** — eBay product listings for secondary-market pricing.
- **Walmart Scraper** — Walmart product records for retail assortment analysis.
- **Best Buy Scraper** — Best Buy product data by search, category, or SKU.
- **Flipkart Scraper** — Flipkart product listings for Indian e-commerce research.

### Data Scrapers support

Need an additional field, record type, or export workflow? Contact Data Scrapers at stardustspotlight@gmail.com. Include a sample source URL, the required fields, the expected record volume, and your preferred delivery format.

# Actor input Schema

## `startUrls` (type: `array`):

Zara category or product URLs, for example https://www.zara.com/de/en/man-jeans-l659.html?v1=2432131. The country and language in the path select the store and its currency.

## `searchQueries` (type: `array`):

Product search terms, for example shorts or linen shirt. Uses the Storefront field. You can combine these with start URLs.

## `storefront` (type: `string`):

Market for search queries, as country/language. For example de/en (Germany, English, EUR), us/en (United States, USD), or uk/en (United Kingdom, GBP). Category and product URLs use the market in the URL instead. Currency on each product comes from that store.

## `section` (type: `string`):

Department for search queries. Category URLs already belong to one department.

## `filters` (type: `object`):

Same filters as the Zara grid. colour and size match the on-site labels (for example Black or 36). priceMin and priceMax are in the store currency. Other on-site filter ids can be passed as extra keys, for example {"color": \["Black"], "size": \["36"], "priceMin": 20, "priceMax": 80}.

## `sort` (type: `string`):

Sort order. Featured keeps the site order. Price and New match the Zara sort control.

## `includeProductDetails` (type: `boolean`):

Fetch description, composition, colours, and sizes for each product. Charged as a product-extra event in addition to the product event. Detail requests run in parallel, each with a new proxy.

## `detailConcurrency` (type: `integer`):

How many product detail requests to run at once when Include Product Details is enabled.

## `maxItems` (type: `integer`):

Maximum number of products to scrape. Use 0 for no limit.

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

Proxy settings. Residential proxies are recommended. When product details are enabled, each detail request uses a new proxy.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.zara.com/de/en/man-jeans-l659.html?v1=2432131"
    }
  ],
  "searchQueries": [
    "shorts"
  ],
  "storefront": "de/en",
  "section": "ALL",
  "filters": {},
  "sort": "default",
  "includeProductDetails": false,
  "detailConcurrency": 8,
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

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

Dataset of Zara products

## `runStats` (type: `string`):

Product counts and timestamps for this run

# 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 = {
    "startUrls": [
        {
            "url": "https://www.zara.com/de/en/man-jeans-l659.html?v1=2432131"
        }
    ],
    "searchQueries": [
        "shorts"
    ],
    "storefront": "de/en",
    "filters": {},
    "maxItems": 20,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("datascrapers/zara-scraper").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 = {
    "startUrls": [{ "url": "https://www.zara.com/de/en/man-jeans-l659.html?v1=2432131" }],
    "searchQueries": ["shorts"],
    "storefront": "de/en",
    "filters": {},
    "maxItems": 20,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("datascrapers/zara-scraper").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 '{
  "startUrls": [
    {
      "url": "https://www.zara.com/de/en/man-jeans-l659.html?v1=2432131"
    }
  ],
  "searchQueries": [
    "shorts"
  ],
  "storefront": "de/en",
  "filters": {},
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call datascrapers/zara-scraper --silent --output-dataset

```

## MCP server setup

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

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/BaZORFIM8MeHMlbqI/builds/nVHp6ALKseBtWxHhi/openapi.json