Turn Vestiaire Collective's public pre-owned luxury resale marketplace into structured JSON — keyword, category, brand, and condition search with live facet counts and a price range across the full filtered result set, full listing detail with seller summary, a seller's public storefront profile, and the complete universe/category and condition-grade taxonomy. Normalized JSON, credential-free.
Search Vestiaire Collective's pre-owned luxury resale catalog, get listing and seller detail, and browse the category and condition taxonomy as structured JSON.
Familias de endpoints
6
Parámetros documentados
19
Ejemplos
8
Snapshot en vivo del catálogo
Endpoints activos
8
Métodos
GET
Parámetros obligatorios
12
Referencias de esquema
8
{
"platform": "Vestiaire Collective",
"endpoint": "vestiaire-search",
"method": "GET",
"path": "/vestiaire/search",
"auth": "apiKey"
}Casos de uso
Search Vestiaire Collective's pre-owned luxury resale catalog, get listing and seller detail, and browse the category and condition taxonomy as structured JSON.
Usa los endpoints de Vestiaire Collective para convertir pre-owned luxury resale pricing and condition-grade research en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Vestiaire Collective para convertir category and brand demand tracking en solicitudes API repetibles con inputs documentados y respuestas JSON.
Usa los endpoints de Vestiaire Collective para convertir seller and marketplace-supply monitoring en solicitudes API repetibles con inputs documentados y respuestas JSON.
Ejecución gestionada
Cada cifra de abajo se lee directamente del catálogo de endpoints en vivo de Vestiaire Collective — 8 endpoints, 19 parámetros de solicitud documentados y 8 esquemas de respuesta publicados — el mismo catálogo contra el que corren Docs y Playground.
8 documented Vestiaire Collective endpoints, grouped into 8 request families — Brands, Categories and Conditions, plus 5 more.
19 request parameters are documented across those Vestiaire Collective endpoints, 12 of them required — the full input contract is public before you write any integration code.
8 of the 8 Vestiaire Collective endpoints ship a recorded example response, and 8 carry a documented response schema — you can code against the real JSON before the first request.
Vestiaire Collective endpoints document their error responses (400, 404, 429, 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.
8 hosted MCP tools back the Vestiaire Collective endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Mapa de cobertura
/vestiaire/brands
/vestiaire/categories
/vestiaire/conditions
/vestiaire/product
/vestiaire/search
/vestiaire/search-sellers
Catálogo de endpoints
/vestiaire/searchSearches Vestiaire Collective's public pre-owned luxury resale catalog by keyword, category, brand, and condition, with sort and pagination. `sort` values: `relevance`, `price_asc`, `price_desc`, `recency`. `category_id` and `condition_id` come from /vestiaire/categories and /vestiaire/conditions. `page` * `per_page` cannot exceed an offset of 1000 (the upstream service's own pagination limit) -- narrow the query instead of paging deeper. Public data, sourced from Vestiaire Collective's own search service.
Notas de la respuesta
- `facets` summarizes brand/category/condition counts for the current query and filters — a useful way to discover a `brand_id` before narrowing a search further. - `price_range` is the minimum/maximum price (in cents) across the current filtered result set, not just the current page. - Each item's `url` is usable directly as the `path` query parameter to [`/vestiaire/product`](vestiaire-product.md). - An invalid `sort` or `condition_id` returns `400` before any upstream request is made. - Vestiaire Collective's own search service caps how deep a query can page: `page` × `per_page` cannot exceed an offset of 1000. Requesting a deeper page returns `400` before any upstream request is made — narrow the query with `q`, `category_id`, `brand_id`, or `condition_id` instead of paging further.
Herramienta MCP vestiaire_search
/vestiaire/productReturns a single Vestiaire Collective listing's public detail: price, brand, category, condition, material, color, size, seller summary, and photos. `path` is the listing's URL or site-relative path, as returned by /vestiaire/search's `url` field -- the numeric id alone cannot be resolved to a page. Public data, sourced from Vestiaire Collective's own listing page.
Notas de la respuesta
- `seller` is a public summary only (username, country, badge, and aggregate sold/listed counts) — no contact or account information. - An unresolvable `path` returns `404`.
Herramienta MCP vestiaire_product
/vestiaire/sellerReturns a Vestiaire Collective seller's public storefront profile: username, country, segment, aggregate sold/listed/bought counts, and follower/following counts. `id` is the numeric seller id, as returned by /vestiaire/search's `seller_id` field or /vestiaire/product's `seller.id`. Public data, sourced from Vestiaire Collective's own seller profile page.
Notas de la respuesta
- Only what any visitor sees on the seller's own public page — no contact or account information. - An unresolvable `id` returns `404`.
Herramienta MCP vestiaire_seller
/vestiaire/categoriesReturns the full Vestiaire Collective category taxonomy: universes (Women, Men, Kids) at the root, with up to three nested category levels beneath each. Every id returned here is accepted by /vestiaire/search's category_id filter.
Herramienta MCP vestiaire_categories
/vestiaire/conditionsReturns the fixed set of condition ids accepted by /vestiaire/search's condition_id filter, with each id's display name and current listing count.
Herramienta MCP vestiaire_conditions
/vestiaire/brandsReturns Vestiaire Collective's full brand directory (id, name, url), not just brands with active listings for a given search -- resolves search's otherwise-opaque brand_id filter, and a search response's facets.brands, to the complete set of valid ids. Public data, sourced from Vestiaire Collective's own brand-directory page.
Notas de la respuesta
- `brands` is sorted by numeric `id` for a deterministic order. - `id` is the same id `/vestiaire/search`'s `brand_id` filter accepts. - Only active brands are included; inactive/delisted brand entries are filtered out.
Herramienta MCP vestiaire_brands
/vestiaire/search-sellersFinds Vestiaire Collective sellers by username or first name. A matched result's id can be passed directly to GET /vestiaire/seller for that seller's full public storefront profile. Public data, sourced from Vestiaire Collective's own member-search service.
Notas de la respuesta
- `name` reflects whatever the seller has set as their first name; it may differ from `username`. - `avatar_url` is omitted when the seller has no profile picture set. - A missing `q` returns `400` before any upstream request is made. - A query with no matching sellers returns `200` with `"sellers": []`.
Herramienta MCP vestiaire_search_sellers
/vestiaire/suggestReturns Vestiaire Collective's own search-box autocomplete suggestions for a partial query: matching brands plus completed search phrases. Public data, sourced from Vestiaire Collective's own search-suggestions service.
Notas de la respuesta
- `brands` lists brand matches for the query, each with the same `id` accepted by [`GET /vestiaire/search`](vestiaire-search.md)'s `brand_id` filter. - `suggestions` lists completed search phrases (plain strings) for the query. - A missing `q` returns `400` before any upstream request is made. - A query with no matches returns `200` with empty `brands`/`suggestions`.
Herramienta MCP vestiaire_suggest
APIs relacionadas
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.
Cómo hacer scraping de Vestiaire Collective
Crawlora's five Vestiaire Collective endpoints return search, listing, seller, category, and condition data as normalized JSON with one API key — categories and conditions are the two discovery endpoints for search's own category_id and condition_id filters, both cached for reference-data stability.
Call /vestiaire/categories for the full universe (Women, Men, Kids) and up to three nested category levels beneath each, and /vestiaire/conditions for the fixed 5-tier condition scale (ids 1 through 5, Never worn with tag through Fair condition) — both with live listing counts, and both exactly what /vestiaire/search's category_id and condition_id filters accept.
Send q, category_id, brand_id, and/or condition_id to /vestiaire/search, with sort (relevance, price_asc, price_desc, or recency) and page/per_page (up to 60 per page). facets in the response summarizes brand/category/condition counts for the current filters — a way to discover a brand_id before narrowing further — and price_range reports the min/max price in cents across the whole filtered set, not just the current page.
Pass a search result's own url to /vestiaire/product's path parameter for full detail — brand, category, condition, material, color, size, and a public seller summary. The numeric listing id alone cannot be resolved to a page, since Vestiaire Collective's URLs are SEO slugs, not derivable from the id.
Pass a seller's numeric id (from a search result's seller_id or a product's seller.id) to /vestiaire/seller for their public storefront profile — username, country, segment, and aggregate sold/listed/bought/follower counts, the same as any visitor sees on their profile page.
On 2026-10-30 /vestiaire/brands returned 13,691 brands in one response, categories returned 3 universes, and conditions returned 5 conditions with counts.
Agent Skills
Instala un agent skill de Crawlora y tu agente obtiene datos de Vestiaire Collective como JSON mediante la API documentada, sin escribir un scraper. Estos skills cubren Vestiaire Collective:
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-researchPreguntas frecuentes
page times per_page cannot exceed an offset of 1000 — the upstream search service's own paging cap. Requesting a deeper page returns 400 before any upstream request is made; narrow with q, category_id, brand_id, or condition_id instead of paging further.
Run a keyword or category search first and read the response's facets.brands field, which lists matching brands with their id and live count. There is no separate standalone brand-directory endpoint — facets is the discovery path.
/vestiaire/conditions returns the fixed 5-tier scale: 1 (Never worn, with tag), 2 (Never worn), 3 (Very good condition), 4 (Good condition), and 5 (Fair condition), each with a live listing count. Pass any id as condition_id to /vestiaire/search.
Cents in price_range and price_cents fields (e.g. price_cents: 270000 is $2,700.00) — divide by 100 before displaying or comparing. This matches how the upstream search service itself reports price.
No — only your Crawlora API key. Search, listing, seller, category, and condition data are collected from Vestiaire Collective's public, credential-free marketplace surface.