Multi-market pricing and assortment research
Use Zalando endpoints to turn multi-market pricing and assortment research into repeatable API requests with documented inputs and JSON responses.
Turn public Zalando storefronts into structured fashion-retail data — keyword search, category and brand browsing, product detail by SKU, and search-box autocomplete, each scoped to one of 25 European country storefronts. Credential-free.
Search Zalando fashion storefronts across 25 European markets and get product detail, category browsing, and autocomplete as structured JSON.
Endpoint families
5
Documented params
13
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
13
Schema refs
5
{
"platform": "Zalando",
"endpoint": "zalando-search",
"method": "GET",
"path": "/zalando/search",
"auth": "apiKey"
}Use cases
Search Zalando fashion storefronts across 25 European markets and get product detail, category browsing, and autocomplete as structured JSON.
Use Zalando endpoints to turn multi-market pricing and assortment research into repeatable API requests with documented inputs and JSON responses.
Use Zalando endpoints to turn category and brand catalog monitoring into repeatable API requests with documented inputs and JSON responses.
Use Zalando endpoints to turn search-query autocomplete for demand research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Zalando endpoint catalog — 5 endpoints, 13 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented Zalando endpoints, grouped into 5 request families — Category, Markets and Product, plus 2 more.
13 request parameters are documented across those Zalando endpoints, 13 of them required — the full input contract is public before you write any integration code.
5 of the 5 Zalando endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Zalando endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
5 hosted MCP tools back the Zalando endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/zalando/category
/zalando/markets
/zalando/product
/zalando/search
/zalando/suggest
Endpoint catalog
/zalando/searchSearches a Zalando country storefront by keyword and returns normalized result cards with price, brand, and image. Returns the first page of results as rendered by Zalando plus the upstream total_count; deeper pagination is not yet supported. market is required (there is no default storefront) and accepts 25 country storefronts — see zalando-markets for the full current list with domains.
MCP tool zalando_search
/zalando/categoryBrowses a Zalando category or brand listing by URL slug (e.g. shoes, womens-dresses, on-running) and returns the same normalized result cards as zalando-search, plus the category's upstream total_count. Category slugs are market-specific (each storefront uses its own local-language slug, e.g. "shoes" on de/gb, "chaussures" on fr, "scarpe" on it) — take them from that market's own site navigation or a product's url field. market is required (there is no default storefront) and accepts 25 country storefronts — see zalando-markets for the full current list with domains.
MCP tool zalando_category
/zalando/productReturns normalized product details for one Zalando product, including brand, description, images, and per-size price/availability/GTIN. Pass the sku returned by zalando-search or zalando-category; Zalando's own site search resolves the sku to its canonical product page. market is required and must match the storefront the sku was found in (there is no default, and a sku is generally only listed for sale on the market(s) that carry it) — see zalando-markets for the full reference list.
MCP tool zalando_product
/zalando/suggestReturns Zalando's own search-box query completions for a partial keyword, e.g. "running sho" -> "running shoes", "running shoes nike". market is required (there is no default storefront) and accepts 25 country storefronts — see zalando-markets for the full current list with domains.
MCP tool zalando_suggest
/zalando/marketsReturns the Zalando country storefronts currently supported by the required market parameter on zalando-search, zalando-category, and zalando-product, with each market's domain. Static, credential-free metadata with no upstream request.
MCP tool zalando_markets
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
How to scrape Zalando
Zalando runs a separate storefront per European country. Crawlora's Zalando endpoints take a required `market` parameter (e.g. `de`, `fr`, `gb`) alongside the query and return normalized JSON with one API key — no HTML parsing required.
Call /zalando/markets for the full list of supported country storefronts and domains — every other Zalando endpoint requires an explicit `market`.
Send a keyword to /zalando/search, or a category/brand slug to /zalando/category, both scoped to a market.
Pass a product SKU (from a search or category result) and the same market to /zalando/product.
Use /zalando/suggest for search-box query completions, or re-run searches on a schedule to track pricing and assortment.
FAQ
Send a keyword and a market code (e.g. `de`, `fr`, `gb`) to Crawlora's /zalando/search endpoint and get normalized product results as structured JSON.
Zalando runs a fully separate storefront, catalog, and pricing per European country, with no default. Call /zalando/markets for the current list of supported markets and domains.
No Zalando account or API key is required from the caller — only your Crawlora API key.
Not an open one. Zalando's Partner API is for approved business integrations only — it requires submitting an application and going through an approval process before you get OAuth credentials, and new apps start restricted to sandbox mode. Crawlora's Zalando endpoints return search, product, category, and autocomplete data across all 25 European markets as structured JSON with a single API key, no partner application required.