Multi-brand outlet pricing and discount monitoring
Use YOOX endpoints to turn multi-brand outlet pricing and discount monitoring into repeatable API requests with documented inputs and JSON responses.
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.
Endpoint families
4
Documented params
18
Examples
4
Live catalog snapshot
Active endpoints
4
Methods
GET
Required params
7
Schema refs
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.
Use YOOX endpoints to turn multi-brand outlet pricing and discount monitoring into repeatable API requests with documented inputs and JSON responses.
Use YOOX endpoints to turn department-level category and designer coverage research into repeatable API requests with documented inputs and JSON responses.
Use YOOX endpoints to turn new-arrival and assortment tracking into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live YOOX endpoint catalog — 4 endpoints, 18 documented request parameters, and 4 published response schemas — the same catalog Docs and Playground run against.
4 documented YOOX endpoints, grouped into 4 request families — Categories, Designers and Product, plus 1 more.
18 request parameters are documented across those YOOX endpoints, 7 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.
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.
/yoox/categories
/yoox/designers
/yoox/product
/yoox/search
Endpoint catalog
/yoox/searchSearches or browses YOOX's public catalog with department, category, designer, color, size, price, sale, sort, and page filters.
Response notes
- 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. Example response: ```json {"code":200,"msg":"OK","data":{"department":"women","query":"gucci","page":1,"limit":48,"count":1,"products":[{"id":"123456","name":"Gucci handbag","brand":"Gucci","price":950,"currency":"USD","in_stock":true}]}} ```
MCP tool yoox_search
/yoox/productReturns the public product detail identified by a YOOX product URL.
Response notes
- 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. Example response: ```json {"code":200,"msg":"OK","data":{"id":"123456","url":"https://www.yoox.com/us/women/product/123456","name":"Designer handbag","brand":"Gucci","price":950,"currency":"USD","in_stock":true}} ```
MCP tool yoox_product
/yoox/categoriesReturns department-scoped category slugs discovered from YOOX navigation. Every returned slug is valid for yoox-search.
Response notes
- 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. Example response: ```json {"code":200,"msg":"OK","data":{"departments":[{"department":"women","categories":[{"name":"Handbags","slug":"handbags","url":"https://www.yoox.com/us/women/handbags/shoponline"}]}]}} ```
MCP tool yoox_categories
/yoox/designersReturns the department-scoped designer slugs discovered from YOOX navigation. Every returned slug is valid for yoox-search.
Response notes
- 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. Example response: ```json {"code":200,"msg":"OK","data":{"department":"women","count":2,"designers":[{"name":"Balenciaga","slug":"balenciaga"},{"name":"Gucci","slug":"gucci"}]}} ```
MCP tool yoox_designers
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 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.
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.
FAQ
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.