INQUIRE NOW
INQUIRE NOW
REST API · Structured JSON · Zalando fashion marketplace data

Zalando Product Data API

Send a Zalando product URL or a search query to one REST endpoint and get structured JSON back — title, brand, price, discount, sizes, colours, availability and more. No proxies to rotate, no headless browsers to run and no HTML to parse. Use the data to feed pricing models, digital shelf dashboards, catalogue tools and European fashion market research.

  • Product, brand and category data
  • Price, original price and discount fields
  • Ratings and review counts
  • Size, colour and availability fields
  • Country-specific prices and currencies
  • Scheduled monitoring with webhooks
/v1/productIllustrative sample
# Request (replace the key and URL with your own)
POST https://api.webfusiondata.com/v1/product
Authorization: Bearer $WFD_API_KEY

{ "url": "https://www.zalando.de/example-brand-sneaker-ex123a0b0-a11.html",
  "country": "DE" }

# Response (sample data, not a live listing)
{
  "product_id": "123456",
  "marketplace": "DE",
  "title": "Example Sneaker",
  "brand": "Example Brand",
  "price": { "amount": 79.95, "currency": "EUR" },
  "original_price": 99.95,
  "availability": "Available",
  "rating": 4.5,
  "product_url": "https://www.zalando.de/"
}

Sample values for illustration only. Exact field names and nesting for your Zalando scope are confirmed in the API reference issued with your key.

How to read this page: Documented = described on our Ecommerce Scraping API page; Illustrative = sample data or example code, not live output; Confirm at onboarding = depends on your Zalando scope and is settled with our team before you build on it.

What Is the Zalando Product Data API?

A Zalando Product Data API lets your software request information about Zalando fashion and lifestyle listings and receive it as structured data instead of a web page. You send a product URL or a search query, and get JSON with named fields such as title, brand, price, discount, sizes, colours, rating, review count and availability. Every response follows the same schema, so it can go straight into a database, dashboard or pricing model.

Behind that request sits a collection process: our infrastructure loads the listing, handles proxies and CAPTCHAs, renders JavaScript, extracts fields with site-specific parsers and validates them before anything is returned. Larger jobs run asynchronously, with results sent to a webhook or storage bucket. You work with the API; we operate the collection layer.

Fashion brands, retailers and analysts use the data for pricing and discount analysis, competitor research, digital shelf tracking, catalogue management and market intelligence. Our price monitoring and price intelligence services build on this kind of data.

How the Zalando API Works

Six steps from choosing a marketplace to using the data in your own systems.

Your application WebFusion Data API Collection & parsing layer Validated JSON Database · dashboard · app
1

Select marketplace and data

Confirm the Zalando products you want to track and how you will look them up: a product page URL, a URL built from a product slug and article code, or a keyword or category search.

List the fields you need now, so the scope can be confirmed against what the marketplace exposes.

2

Configure the request

Build a JSON body with url (or site and query) and an optional country.

Pick the endpoint: /v1/product for one listing, /v1/search for result lists, /v1/monitor for scheduled tracking, /v1/bulk for batches.

3

Authenticate

Pass your API key as a bearer token in the Authorization header.

Start in the sandbox, which returns sample responses, so you can test your integration before spending live request credits.

4

Process and retrieve

Our infrastructure fetches the listing, renders it, extracts the fields and validates them. Single lookups return synchronously.

Bulk jobs return a job ID you can check with /v1/status/:job_id or receive through a webhook.

5

Receive structured data

JSON is the default response format. Bulk export jobs can also be delivered as CSV or XLSX.

Each record carries a capture timestamp (crawled_at) so you always know how fresh the values are, which matters during sale events and flash discounts when prices change quickly.

6

Integrate into your systems

Write results to a database, load them into a BI dashboard, trigger alerts from webhooks or schedule recurring checks with monitors.

See Integration and Data Delivery for a worked example.

Key Zalando API Features

What the Zalando Product Data API does in practice, and how much of it is already documented versus settled per project.

PD

Product, brand and category data

Returns the core listing record: title, brand, category (clothing, shoes, accessories and more), images, colour, size range and material or composition where shown. Use it to build or audit a catalogue, group results by brand or department and map Zalando listings to your own taxonomy.

Documented
ID

Product URL and ID-based lookup

Zalando product URLs typically end in an article code followed by .html, so a list of slugs and article codes can be turned into product URLs and submitted. The product identifier is returned in the response for matching.

URL-based: documentedDedicated product ID parameter: confirm
$

Price and sale monitoring

Captures the current price, original price, discount percentage and currency (EUR or local), and can register a listing for scheduled checks with a webhook when a value changes. Useful for repricing inputs, MAP checks and sale-event tracking.

Documented
★

Ratings and review data

Returns the aggregate rating and review count for each listing, so you can compare quality signals across competing products and track movement over time.

Rating & count: documentedReview text: confirm
OF

Offers, delivery and returns data

Returns promotional offers, delivery options and returns information displayed on the listing, where shown. Helps compare the true effective price of competing listings.

Where displayedDelivery by country: confirm
AV

Listing availability data

Returns the displayed stock status for the product and each colour and size where exposed. Supports out-of-stock alerts and availability reporting.

Documented
MP

Marketplace-specific data access

A country parameter sets the market for the request. Zalando runs separate country sites, so prices, currency, sizes and availability depend on the country you select; each site is confirmed at onboarding.

Country parameter: documentedMarketplace list: confirm
JS

Structured API responses

Fields are type-checked and normalised into a consistent schema, with automated checks that catch malformed responses before they reach you.

Documented
AU

Automated data delivery

Schedule recurring monitors, receive webhook callbacks, or request bulk exports to cloud storage, so data arrives without manual pulls.

Documented

Zalando Product Data Fields

The fields the Zalando product data extraction returns, what each one means and what teams do with it. Field availability follows what the listing displays on the selected marketplace.

Data FieldDescriptionBusiness ApplicationAvailability
product_idZalando article code, taken from the product URL (the code before .html)Product identification, de-duplicationCore
titleName of the listed productCatalogue managementCore
brand / categoryBrand and category shown on the listingBrand analysis, category benchmarkingCore
price.amount / price.currencyDisplayed current price and its currency (EUR or local currency)Price comparison, repricing inputsCore
original_price / discountOriginal price and displayed discount percentageMarkdown and promotion analysisWhere displayed
sizes / coloursSizes and colours offered, with stock status per size where exposedSize-level availability trackingWhere displayed
material / compositionMaterial composition and care detailsContent benchmarkingWhere displayed
rating / review_countStar rating and number of ratings and reviewsProduct research, sentiment analysisWhere displayed
reviews (text)Individual review contentSentiment and NLP pipelinesConfirm at onboarding
offersPromotional offers and discount messagesPromotion trackingWhere displayed
availabilityDisplayed stock statusAvailability monitoringCore
deliveryDelivery and returns information shown for the selected countryServiceability checksConfirm at onboarding
product_url / marketplaceListing URL and the marketplace it came fromReference and validationCore
crawled_atTimestamp of data captureFreshness checks, time seriesCore

Core = part of the standard field set on our ecommerce API. Where displayed / available / exposed = returned when the listing on that marketplace shows it, so it can be empty for some listings. Confirm at onboarding = settled per project. Images and the product description are also returned. Field names are illustrative; your API reference is the source of truth.

Zalando API Endpoints and Request Parameters

The Zalando Product Data API uses the same versioned endpoints as the Ecommerce Scraping API. Zalando-specific parameter names that are not yet published are marked as illustrative.

EndpointPurposeParametersExpected response
POST /v1/product
Documented
Structured data for a single product URL: price, discount, sizes, colours, rating, availability and the full attribute set. Required: url
Optional: country; a dedicated product_id field is a confirm
One JSON product record, returned synchronously.
POST /v1/search
Documented
Keyword or category search on a target site, returned as a structured result list. Required: site (e.g. "zalando"), query
Optional: country
JSON with query, result_count and a results array.
POST /v1/monitor
Documented
Registers a listing for scheduled price and stock monitoring with webhook notifications. Required: url
Optional: webhook URL and check frequency names: confirm
A monitor ID you use to read tracked data later.
GET /v1/monitor/:id
Documented
Latest tracked data and change history for one monitored listing. Required: id (path) JSON with the current values and recorded changes.
POST /v1/bulk
Documented
Submits a batch of URLs for asynchronous processing; results go to storage or a webhook. Required: list of URLs
Optional: delivery destination and format (JSON, CSV or XLSX) names: confirm
A job ID, then results via webhook or storage export.
GET /v1/status/:job_id
Documented
Status and progress of an asynchronous crawl or bulk export. Required: job_id (path) JSON with job state and progress.

Common validation errors

SituationTypical HTTP statusHow to fix it
Missing or malformed url400Send a full Zalando product URL, including the https:// prefix.
Unsupported site or country value400 / 422Check site and country against the marketplaces confirmed for your account.
Missing or invalid API key401Send Authorization: Bearer <key> and check the key belongs to the right environment (sandbox or live).
Listing not found or discontinued404 or an empty recordVerify the product URL or slug; products can be discontinued, delisted or temporarily unavailable.
Request limit exceeded429Wait, then retry with backoff. Response headers show your remaining quota for the window.
Temporary processing failure5xxRetry with exponential backoff; for large volumes use /v1/bulk instead of many synchronous calls.

Status codes follow common REST conventions (429 is the one shown in our published dashboard example). The exact codes and error bodies are listed in the API reference supplied with your key.

Sample API Request and JSON Response

Two common calls and what comes back. Illustrative sample data — not live listing information.

1 · Look up one product
curl -X POST https://api.webfusiondata.com/v1/product \
  -H "Authorization: Bearer $WFD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://www.zalando.de/example-brand-sneaker-ex123a0b0-a11.html",
    "country": "DE"
  }'
2 · Search Zalando by keyword
curl -X POST https://api.webfusiondata.com/v1/search \
  -H "Authorization: Bearer $WFD_API_KEY" \
  -d '{"site": "zalando", "query": "white sneakers", "country": "DE"}'
Parameters used: url or site + query select what to fetch; country selects the marketplace. The key stays in an environment variable — never hard-code it or ship it in client-side code.
Response to request 1Illustrative
{
  "product_id": "123456",
  "marketplace": "DE",
  "title": "Example Sneaker",
  "brand": "Example Brand",
  "price": { "amount": 79.95, "currency": "EUR" },
  "original_price": 99.95,
  "discount": { "percent": 20 },
  "availability": "Available",
  "rating": 4.5,
  "review_count": 1280,
  "variant": "White, EU 42",
  "product_url": "https://www.zalando.de/",
  "crawled_at": "2026-01-15T09:30:00Z"
}
Response to request 2Illustrative
{
  "query": "white sneakers",
  "result_count": 48,
  "results": [
    { "title": "Example Sneaker", "price": 59.95,
      "rating": 4.4, "in_stock": true }
  ]
}

The generic search sample on our Ecommerce Scraping API page uses a flat price number and an in_stock flag, while the product example above nests price under an object. The final Zalando schema is confirmed in your API reference.

Supported Zalando Marketplaces

Zalando runs separate country sites, so choose the market with the country parameter. We do not claim coverage beyond what is confirmed during onboarding, and requests outside that scope are rejected rather than guessed.

MarketplaceZalando domainLocal currencyStatus for the API
Germanyzalando.deEURConfirm at onboarding
United Kingdomzalando.co.ukGBPConfirm at onboarding
Francezalando.frEURConfirm at onboarding
Italyzalando.itEURConfirm at onboarding
Spainzalando.esEURConfirm at onboarding
Netherlandszalando.nlEURConfirm at onboarding

This is a reference list of well-known Zalando country sites, not a coverage guarantee. Need another Zalando country site or app? Tell us and we will confirm feasibility.

Why it matters: The country you choose sets the currency, language, listed sizes and brands, and the prices shown, and prices can change during sale events and promotions. Delivery options, returns terms and availability can also vary by country, so tell us which country sites you need. Read each response against its crawled_at timestamp.

Authentication, Rate Limits and Error Handling

What is published today, and what we give you in writing before you go live. We do not publish numeric limits, latency or uptime figures on this page.

TopicHow it worksStatus
AuthenticationYour API key is sent as a bearer token in the Authorization header. Use the sandbox key while testing.Documented
Limits and concurrencyPer-minute limits and concurrent-request allowances scale with your plan; response headers show your remaining quota. Use /v1/bulk for very large volumes.DocumentedNumbers: your plan
Validation and errorsMalformed or missing parameters are rejected with a standard HTTP error (see Endpoints), and responses are schema-checked before delivery.Exact codes: API reference
Timeouts and retriesSet a client timeout and retry reads on 429 and 5xx with exponential backoff. Move long work to /v1/bulk and /v1/status/:job_id, and avoid blind retries of POST /v1/monitor or /v1/bulk.Recommended practice
PaginationSearch returns a result_count and result list. Pagination for deeper results is scoped per project.Confirm at onboarding
Usage monitoringAn account dashboard shows request volume, latency, success rate and job status.Documented

Integration and Data Delivery

Connect the API to ecommerce applications, internal databases, BI dashboards, reporting systems and analytics pipelines. The pattern is the same each time: a request layer, a place to store results and a schedule.

Integration workflow

1

Scope and test

Agree marketplaces, fields and refresh frequency, then call the sandbox with a few sample listings.

2

Build the request layer

Put authentication, timeouts and retry backoff in one small client module your whole team reuses.

3

Store the results

Upsert records by product ID, and keep every crawled_at timestamp to build a time series.

4

Schedule and alert

Use monitors and bulk jobs, act on webhooks, and connect the table to your dashboards and reports.

Example: fetch a listing and store its price Illustrative

Python · requests + sqlite3
import os, sqlite3, requests

API = "https://api.webfusiondata.com/v1/product"
HEADERS = {"Authorization": f"Bearer {os.environ['WFD_API_KEY']}"}

def fetch(slug):
    body = {
        "url": f"https://www.zalando.de/{slug}.html",
        "country": "DE",
    }
    r = requests.post(API, json=body, headers=HEADERS, timeout=60)
    r.raise_for_status()
    return r.json()

db = sqlite3.connect("zalando_prices.db")
db.execute("CREATE TABLE IF NOT EXISTS prices "
           "(product_id TEXT, amount REAL, currency TEXT, at TEXT)")

for slug in ["example-brand-sneaker-ex123a0b0-a11"]:
    item = fetch(slug)
    db.execute("INSERT INTO prices VALUES (?, ?, ?, ?)", (
        item["product_id"],
        item["price"]["amount"],
        item["price"]["currency"],
        item.get("crawled_at"),
    ))
db.commit()

Delivery options

JSON

Default response format for every endpoint.

Documented

CSV, Excel and cloud storage

Bulk export jobs delivered as CSV or XLSX to S3, GCS or your own bucket.

Documented

Webhooks and scheduled monitors

Callbacks when a job completes or a tracked value changes, plus recurring checks through /v1/monitor.

Documented

Database push, SDKs and no-code

Managed warehouse connectors, client libraries and no-code paths.

Languages: confirm

Listed on the Ecommerce Scraping API page; availability for your Zalando scope is confirmed during onboarding. See also the AI Parser and ecommerce datasets. Related: product availability and MAP monitoring.

FAQs

Zalando Product Data API Frequently Asked Questions

What is the Zalando Product Data API?

It is a REST API from WebFusion Data that returns structured JSON for Zalando listings. You send a product URL, or a search query, and receive fields such as title, brand, price, discount, sizes, colours, rating and availability. It runs on the same endpoints and infrastructure as our Ecommerce Scraping API, so you do not run proxies, browsers or parsers yourself.

What product information can it provide?

Core fields include product ID, title, brand, category, price and currency, availability, images, product URL, marketplace and a capture timestamp. Original price, discount percentage, rating, review count, sizes, colours, composition and offers are returned where the listing displays them. Review text and delivery or returns details by country are confirmed per project. The data fields table shows each one.

Can I retrieve data from a Zalando product URL or ID?

Yes, through the product URL. Zalando product URLs end in an article code followed by .html, so you build the URL from your slug and article code and submit it to /v1/product with country set to DE. The product identifier is returned in the response so you can match records. Whether a dedicated product-ID-only parameter, or lookup by SKU or EAN, is available is confirmed at onboarding.

Does it support price monitoring and historical prices?

Yes. POST /v1/monitor registers a listing for scheduled price and stock monitoring with webhook notifications, and GET /v1/monitor/:id returns the latest tracked data and change history. Frequency and volume are scoped to your project. Change history is recorded from the time you register a listing; earlier history is not assumed, so ask if you need a backfill, or store each response with its crawled_at timestamp to build your own series.

Does it provide discount and offer data?

Current price, original price and discount percentage are returned where the listing displays them, along with offer messages. Because prices and offers can change quickly during sale events, we confirm availability and the right monitoring frequency with you before you build on it. Delivery and returns details by country depend on your scope.

Which Zalando markets are supported?

Zalando runs separate country sites, so the country parameter selects the market and prices are returned in that market’s currency. Zalando covers many European markets; we do not claim coverage beyond what is confirmed, and availability for your account is confirmed during onboarding. See supported marketplaces.

How does API authentication work?

Each request carries your API key as a bearer token in the Authorization header. Every account includes a sandbox for testing with sample responses. Keep the key on your server, in an environment variable or secrets manager, and never in client-side code.

Which response formats are available?

JSON is the default for all endpoints. Bulk export jobs can also be delivered as CSV or XLSX, to S3, GCS or your own bucket. Webhooks, SDKs and database push options are described in Integration and Data Delivery.

How can I request API access?

Use the Request API Demo button or the form below and tell us the marketplaces, listing volume, fields, refresh frequency and delivery format you need. We confirm the scope and set up access, including the sandbox. You can also email sales@webfusiondata.com or book a consultation.

Question mark illustration

Contact Us Now!

At WebFusionData, we specialize in cutting-edge web scraping solutions to help you unlock valuable insights and drive business growth. Whether you need custom data extraction, real-time monitoring, or large-scale web scraping, our team is here to assist you.

FAQ Illustration

Get In Touch

Ready to get started? Contact us for a personalized quote.