Zara Scraper

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.

{
  "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:

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

{
  "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:

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.