Multi-brand luxury pricing and availability monitoring
Use Farfetch endpoints to turn multi-brand luxury pricing and availability monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Farfetch's public multi-brand luxury marketplace into structured JSON — department-scoped browsing with designer and category filters, the full designer and category directories per department, and full product detail with every size variant, price, and availability. Normalized JSON, credential-free.
Browse Farfetch's luxury multi-brand marketplace by department, designer, and category, and get full product detail as structured JSON.
Endpoint families
4
Documented params
11
Examples
4
Live catalog snapshot
Active endpoints
4
Methods
GET
Required params
8
Schema refs
4
{
"platform": "Farfetch",
"endpoint": "farfetch-search",
"method": "GET",
"path": "/farfetch/search",
"auth": "apiKey"
}Use cases
Browse Farfetch's luxury multi-brand marketplace by department, designer, and category, and get full product detail as structured JSON.
Use Farfetch endpoints to turn multi-brand luxury pricing and availability monitoring into repeatable API requests with documented inputs and JSON responses.
Use Farfetch endpoints to turn designer and category coverage research into repeatable API requests with documented inputs and JSON responses.
Use Farfetch endpoints to turn new-arrival and assortment tracking across brands into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Farfetch endpoint catalog — 4 endpoints, 11 documented request parameters, and 4 published response schemas — the same catalog Docs and Playground run against.
4 documented Farfetch endpoints, grouped into 4 request families — Categories, Designers and Product, plus 1 more.
11 request parameters are documented across those Farfetch endpoints, 8 of them required — the full input contract is public before you write any integration code.
4 of the 4 Farfetch endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Farfetch endpoints document their error responses (400, 404, 500 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 Farfetch 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.
/farfetch/categories
/farfetch/designers
/farfetch/product
/farfetch/search
Endpoint catalog
/farfetch/searchBrowses Farfetch's luxury multi-brand marketplace by department plus a designer and/or category filter (at least one is required), returning normalized listing summaries (name, brand, price, image, availability) and the upstream page count. Public data sourced from Farfetch's own listing pages.
Response notes
- An unrecognized `gender` value, a `designer`/`category` value that isn't a valid Farfetch URL slug, or a request with neither `designer` nor `category` returns `400` before any upstream request is made. Farfetch's bare department page is an editorial landing page, not a product list; use `category=clothing-1` (or another slug from `/farfetch/categories`) to browse a whole department. - Listing pages sit behind Akamai Bot Manager; a persistent block returns `503` rather than an empty result. - Rendering through the bot protection can take up to about 90 seconds; a call that cannot complete in that window returns `503` rather than timing out. Retry later on `503`.
MCP tool farfetch_search
/farfetch/productReturns a Farfetch product's full detail: name, brand, color, description, images, category breadcrumb, and every size variant with its own price and availability. Public data sourced from Farfetch's own product pages.
Response notes
- Rendering through the bot protection can take up to about 90 seconds; a call that cannot complete in that window returns `503` rather than timing out. Retry later on `503`. - An unrecognized `gender` value, or a `slug` that isn't a valid Farfetch URL slug, returns `400` before any upstream request is made. - A slug that does not resolve to a real product returns `404`. - Product pages sit behind Akamai Bot Manager; a persistent block returns `503` rather than an empty result.
MCP tool farfetch_product
/farfetch/designersReturns a department's full designer directory (name, slug, URL). Each slug is usable directly as the designer filter on GET /farfetch/search. Public data sourced from Farfetch's own designer-directory pages.
Response notes
- An unrecognized `gender` value returns `400` before any upstream request is made. - The directory is the department's whole current designer list, not a sample — hundreds of entries per department (recovered counts: 485 for `women`, 289 for `men`, 58 for `kids` as of this endpoint's build; see `notes/farfetch-maintenance.md`).
MCP tool farfetch_designers
/farfetch/categoriesReturns every department's top-level category directory (name, slug, URL). Each slug is usable directly as the category filter on GET /farfetch/search. Public data sourced live from Farfetch's own listing pages.
Response notes
- Each department is fetched independently and in parallel; a fetch failure for one department does not fail the others, and returns that department with an empty `categories` list. - If every department fails (for example during an upstream bot-protection block), the call returns `503` instead of three empty lists. - Pages are rendered behind Akamai Bot Manager, so calls can take up to about 90 seconds; a call that cannot complete in that window returns `503` rather than timing out.
MCP tool farfetch_categories
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 Farfetch
Crawlora's Farfetch endpoints return department categories, designer directories, browse results, and product detail from Farfetch's luxury marketplace as normalized JSON with one API key. Farfetch's strength is detail rather than filtering. /farfetch/product returns every size variant with its own price and availability, and the designer directory is exhaustive: on 2026-09-18 the women's department listed 476 designers, from A BATHING APE® (slug bape) onward.
/farfetch/categories fetches women, men, and kids independently. If one department fails, that department comes back with an empty categories list and the call still succeeds, so check each department's list before relying on it.
/farfetch/designers requires gender and returns every current designer with a name, slug, and URL: 476 for women on 2026-09-18. The slug is what /farfetch/search's designer filter expects.
/farfetch/search takes gender plus optional designer and category, and page walks the listing's total_pages. It has no keyword, price, sale, or sort parameters, so apply those filters in your own code.
/farfetch/product takes gender and the product slug from a search result's id, such as gucci-slide-sandals-with-double-g-item-37690086. It returns brand, color, description, images, a category breadcrumb, and each size variant's price and availability. An invalid slug returns 400 and an unknown product 404.
FAQ
Yes. /farfetch/product lists every size variant with its own price and availability, so you can see when one size is priced differently from another.
No. /farfetch/search filters only by gender, designer, and category. Narrow by price or availability after fetching, or use /farfetch/product for per-size detail.
/farfetch/categories returns that department with an empty categories list instead of failing the whole call. Retry later for that department.