Multi-brand outlet pricing and discount monitoring
Mit YOOX-Endpunkten verwandelst du multi-brand outlet pricing and discount monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Turn YOOX's public multi-brand fashion marketplace into structured JSON — department-scoped category and designer directories for women, men, and kids, keyword or filtered search with color, size, and price, and full product detail with brand, availability, and images. Normalized JSON, credential-free.
Search or browse YOOX's multi-brand catalog by department, get full product detail, and browse the category and designer directories as structured JSON.
Endpunkt-Familien
4
Dokumentierte Parameter
19
Beispiele
4
Live-Katalog-Snapshot
Aktive Endpunkte
4
Methoden
GET
Pflichtparameter
6
Schema-Referenzen
4
{
"platform": "YOOX",
"endpoint": "yoox-search",
"method": "GET",
"path": "/yoox/search",
"auth": "apiKey"
}Use Cases
Search or browse YOOX's multi-brand catalog by department, get full product detail, and browse the category and designer directories as structured JSON.
Mit YOOX-Endpunkten verwandelst du multi-brand outlet pricing and discount monitoring in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit YOOX-Endpunkten verwandelst du department-level category and designer coverage research in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit YOOX-Endpunkten verwandelst du new-arrival and assortment tracking in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-YOOX-Endpunktkatalog — 4 Endpunkte, 19 dokumentierte Request-Parameter und 4 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
4 documented YOOX endpoints, grouped into 4 request families — Categories, Designers and Product, plus 1 more.
19 request parameters are documented across those YOOX endpoints, 6 of them required — the full input contract is public before you write any integration code.
4 of the 4 YOOX endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
YOOX endpoints document their error responses (400, 404 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.
4 hosted MCP tools back the YOOX endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/yoox/categories
/yoox/designers
/yoox/product
/yoox/search
Endpunktkatalog
/yoox/searchSearches or browses YOOX products in the required `department`. Optional filters are `q`, `category`, `designer`, `color`, `size`, `price_min`, `price_max` and `on_sale`; `sort` takes `relevance`, `newest`, `price_asc`, `price_desc` or `discount`; `limit` is 1 to 100. Each product has brand, name, price, currency, stock status, image and URL, with `facets` for colors, sizes and sorts. May return `503`.
Hinweise zur Response
- YOOX pages are rendered through bot protection, so calls can take up to about 80 seconds; a call that cannot complete in that window returns `503` rather than timing out. - While YOOX itself is showing its site-wide maintenance page, calls return `503` with a message saying so. Retry later. - A persistent bot-protection block also returns `503`, never an empty result.
MCP-Tool yoox_search
/yoox/productReturns a YOOX product by item `id`, the path segment before `/item` in a product URL, for example `17734181OO`. The older `url` parameter still works instead. The response has name, brand, price, currency, `in_stock`, description, images and category. Calls can take up to about 80 seconds and return `503` if they cannot finish.
Hinweise zur Response
- YOOX pages are rendered through bot protection, so calls can take up to about 80 seconds; a call that cannot complete in that window returns `503` rather than timing out. - While YOOX itself is showing its site-wide maintenance page, calls return `503` with a message saying so. Retry later. - A persistent bot-protection block also returns `503`, never an empty result.
MCP-Tool yoox_product
/yoox/categoriesLists YOOX categories grouped by department (`women`, `men` and `kids`), each with its name, slug and URL. Every category slug is valid as `category` in YOOX search. Calls can take up to about 80 seconds, and a call that cannot finish, or one made while YOOX shows its maintenance page, returns `503`.
Hinweise zur Response
- YOOX pages are rendered through bot protection, so calls can take up to about 80 seconds; a call that cannot complete in that window returns `503` rather than timing out. - While YOOX itself is showing its site-wide maintenance page, calls return `503` with a message saying so. Retry later. - A persistent bot-protection block also returns `503`, never an empty result.
MCP-Tool yoox_categories
/yoox/designersLists YOOX designers for the required `department` (`women`, `men` or `kids`), with the `count` and each designer's name, slug and URL. Every designer slug is valid as `designer` in YOOX search. A call that cannot finish within about 80 seconds returns `503`, as does one made during YOOX maintenance.
Hinweise zur Response
- YOOX pages are rendered through bot protection, so calls can take up to about 80 seconds; a call that cannot complete in that window returns `503` rather than timing out. - While YOOX itself is showing its site-wide maintenance page, calls return `503` with a message saying so. Retry later. - A persistent bot-protection block also returns `503`, never an empty result.
MCP-Tool yoox_designers
Verwandte APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
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.
So scrapst du YOOX
Crawlora's YOOX endpoints return categories, designers, search results, and product detail from YOOX's off-season designer outlet as normalized JSON with one API key. YOOX sells past-season stock at a discount, and the search endpoint reflects that. It has an on_sale filter and a sort=discount option that ranks listings by markdown size. Farfetch, a full-price marketplace, has neither. YOOX's four routes depend on a required department and on slugs from the directory routes, and the documentation warns that calls can take about 80 seconds or return 503 during maintenance.
Every search is scoped to one department: women, men, or kids. /yoox/categories returns all three departments' category slugs in one response, and /yoox/designers returns one department's designer slugs, such as gucci.
/yoox/search takes the department plus any mix of q, category, designer, color, size, price_min, price_max, and on_sale. Sort with relevance, newest, price_asc, price_desc, or discount, and page with page and limit.
/yoox/product takes the product's full YOOX URL from a search result, not a slug, and returns price, availability, brand, description, images, and category.
YOOX pages are rendered through a headless browser behind Akamai Bot Manager, so calls are slower than plain API requests. A 503 (yoox render failed) means the challenge wasn't cleared, not that nothing matched. Retry with backoff.
search requires a department, and designers accepts women, men or kids. Every category slug from the categories route is valid as category in search, and every designer slug from the designers route is valid as designer.
Calls can take up to about 80 seconds, and a call that cannot finish, or one made while YOOX shows its maintenance page, returns 503. Use long timeouts and retries with backoff.
search takes q, category, designer, color, size, price_min, price_max and on_sale, sorts by relevance, newest, price_asc, price_desc or discount, and limits results to 1 to 100. Each product has brand, name, price, currency, stock status, image and URL, plus facets for colors, sizes and sorts.
product takes the item id, the path segment before /item in a product URL such as 17734181OO; the older url parameter still works.
On 2026-10-30 /yoox/designers and /yoox/search both answered 503 YOOX is currently showing a maintenance page. Retry later; the 503 is not an empty catalog.
Agent Skills
Installiere einen Crawlora Agent Skill, und dein Agent ruft YOOX-Daten als JSON über die dokumentierte API ab, ohne einen Scraper zu schreiben. Diese Skills decken YOOX ab:
Research luxury-fashion and watch resale listings, sold evidence, condition, and seller signals across specialist marketplaces. Use for sourcing or…
npx skills add github.com/Crawlora-org/crawlora-skills --skill luxury-resale-researchFAQ
Call /yoox/search with on_sale=true and sort=discount, scoped to a department and optionally a designer or category. Results are ordered by discount size.
YOOX product pages are addressed by their full URL. Take the url field from a /yoox/search result and pass it unchanged.
The Akamai-protected page could not be rendered for that request, for example yoox render failed. It is a retry signal, not an empty result.
Because a call that cannot finish in about 80 seconds returns 503, as does one made during YOOX maintenance. Retry later.
The path segment before /item in a product URL, for example 17734181OO.