Zalando APIzalando.it ↗
Access Zalando Italy product data via 4 endpoints: search products, browse category listings, fetch full product details, and retrieve homepage images.
What is the Zalando API?
The Zalando Italy API covers 4 endpoints for extracting product data from zalando.it, including search results, category listings, and full product detail pages. The get_product_detail endpoint returns structured fields such as SKU, brand, EUR price, available sizes, color options, and image URLs from any Zalando Italy product page. Whether you need to monitor pricing, aggregate fashion inventory, or browse category listings with a price ceiling, the API maps directly to Zalando Italy's catalog.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/3b3f806c-9410-4fbc-88c5-40e54ef2ed73/get_homepage' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace zalando-it-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.zalando_italy_api import ZalandoItaly, Product, ProductDetail, HomepageImage
client = ZalandoItaly()
# Search for Nike products
for product in client.products.search(query="nike"):
print(product.name, product.brand, product.price, product.url)
# Navigate from a product summary to its full detail
detail = product.details()
print(detail.name, detail.brand, detail.price, detail.sku)
for size in detail.sizes:
print(size)
# Browse category with price filter
for product in client.products.list_by_category(path="/scarpe-uomo/", price_to=100):
print(product.name, product.brand, product.price)
# Get homepage images
homepage = client.homepages.get()
print(homepage.url)
for img in homepage.images:
print(img.url, img.alt)
Fetches the Zalando Italy men's homepage and extracts promotional/editorial images with their alt text descriptions. Returns the final page URL and all featured images found on the page.
No input parameters required.
{
"type": "object",
"fields": {
"url": "string, the final URL of the homepage",
"images": "array of objects with 'url' (image URL) and 'alt' (alt text description)"
},
"sample": {
"data": {
"url": "https://www.zalando.it/uomo-home/",
"images": [
{
"alt": "Due persone camminano su una strada lastricata indossando abbigliamento sportivo e occhiali da sole, una beve un frullato verde.",
"url": "https://img01.ztat.net/ply/assets-landing-pages/production/images/cd64ey4rckeivb49m55u/1780672794006_cd64ey4rckeivb49m55u.jpeg?imwidth=1200"
}
]
},
"status": "success"
}
}About the Zalando API
Product Search and Category Browsing
The search_products endpoint accepts a query string (e.g. 'nike', 'scarpe', 'adidas') and returns a list of matching products, each with name, brand, price, url, and image fields, plus a total count of results. For browsing by category, get_category_listing accepts an optional path parameter such as /scarpe-uomo/ or /abbigliamento-uomo/ and an optional price_to filter (in EUR) to cap results by maximum price. Both endpoints return the same product object shape, making it straightforward to unify search and browse workflows.
Product Detail Extraction
The get_product_detail endpoint takes a full zalando.it product URL and returns a richer set of fields: a sku (product group ID), name, brand, price in EUR, a sizes array of available size strings, a colors array of objects each with a name field, and an images array of URL strings. This makes it suitable for tasks like tracking size availability over time or building a detailed product catalog from Zalando Italy listings.
Homepage and Editorial Images
The get_homepage endpoint requires no inputs and returns the final resolved URL of the Zalando Italy homepage alongside an images array. Each image object contains a url and an alt text string, reflecting the promotional and editorial content Zalando surfaces on its front page. This can be useful for tracking seasonal campaigns or editorial themes.
Coverage Scope
All four endpoints target zalando.it specifically, so data reflects Italian-market pricing (EUR), Italian-language product names, and the Italian regional catalog. Results from search_products and get_category_listing include only the fields surfaced on listing pages; full size and color detail requires a subsequent call to get_product_detail with the product URL.
The Zalando API is a managed, monitored endpoint for zalando.it — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when zalando.it changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official zalando.it API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track EUR price changes for specific products on Zalando Italy using
get_product_detail. - Monitor available sizes for high-demand sneakers across zalando.it product pages.
- Aggregate brand and product listings from a category path like
/scarpe-uomo/with a price ceiling. - Build a fashion price comparison tool using search results from
search_products. - Identify seasonal promotional themes by parsing homepage editorial images and their alt text.
- Feed a product catalog database with structured SKU, brand, color, and image data from Zalando Italy.
- Filter category listings under a specific EUR budget using the
price_toparameter inget_category_listing.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Zalando have an official developer API?+
What does `get_product_detail` return beyond what search results provide?+
search_products and get_category_listing) return name, brand, price, url, and image per product. get_product_detail adds sku (product group ID), a sizes array of available size strings, a colors array with name fields, and a full images array of URL strings — fields only available on the individual product page.Can I filter search results by category or price in `search_products`?+
search_products accepts only a query keyword string and returns matching products without price or category filters. The get_category_listing endpoint supports both a path parameter for category selection and a price_to parameter for a maximum EUR price cap. You can fork this API on Parse and revise it to add filter parameters to the search endpoint.Does the API return product reviews or ratings?+
get_product_detail to add a reviews field.Does the API support pagination for search or category listings?+
page or offset parameter exposed on search_products or get_category_listing. The total field reflects the count of products returned in that single response. You can fork the API on Parse and revise it to add pagination parameters if deeper result sets are needed.