Luxury retail pricing and stock monitoring
Use Gucci endpoints to turn luxury retail pricing and stock monitoring into repeatable API requests with documented inputs and JSON responses.
Join Gucci's merchandising surface to its retail footprint: browse the cumulative category catalogue, resolve size guides and recommendations, inspect product variants, and search public store features within a map viewport across verified storefront markets.
Search Gucci products and store locations, browse categories, size guides, recommendations, product details, and public store records as JSON.
Endpoint families
6
Documented params
32
Examples
10
Live catalog snapshot
Active endpoints
10
Methods
GET
Required params
23
Schema refs
10
{
"platform": "Gucci",
"endpoint": "gucci-search",
"method": "GET",
"path": "/gucci/search",
"auth": "apiKey"
}Use cases
Search Gucci products and store locations, browse categories, size guides, recommendations, product details, and public store records as JSON.
Use Gucci endpoints to turn luxury retail pricing and stock monitoring into repeatable API requests with documented inputs and JSON responses.
Use Gucci endpoints to turn category taxonomy and merchandising research into repeatable API requests with documented inputs and JSON responses.
Use Gucci 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 Gucci endpoint catalog — 10 endpoints, 32 documented request parameters, and 10 published response schemas — the same catalog Docs and Playground run against.
10 documented Gucci endpoints, grouped into 9 request families — Stores, Categories and Category, plus 6 more.
32 request parameters are documented across those Gucci endpoints, 23 of them required — the full input contract is public before you write any integration code.
10 of the 10 Gucci endpoints ship a recorded example response, and 10 carry a documented response schema — you can code against the real JSON before the first request.
Gucci endpoints document their error responses (400, 404, 429 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.
10 hosted MCP tools back the Gucci endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/gucci/stores
/gucci/categories
/gucci/category
/gucci/product
/gucci/recommendations
/gucci/search
Endpoint catalog
/gucci/searchSearches Gucci's US product catalog by keyword using the storefront's public catalog. Results include card-level data and the live total count; per-product colors, materials, sizes, gender, and line are omitted when the search source does not provide them. A genuinely empty result returns a well-formed empty products list. The response's size_facets field lists live size values and counts -- pass one as size on a follow-up call to filter.
Response notes
- A genuinely empty result (e.g. a nonsense query) returns a well-formed empty `products` list with `total_results: 0`, not an error. - `price` and `currency` are always in USD (the US storefront only). - `size_facets` lists every size value present in the response's own result set (i.e. `q`, and `size` if also given), each with its own live product count. - Gucci's current catalog search source returns card-level fields: style code, name, price, images, PDP URL, and stock. Optional per-product fields such as `colors`, `materials`, `sizes`, `gender`, and `line` are omitted when Gucci does not include them in that search response; use `gucci-product` for PDP attributes.
Sampled 14 Oct 2026: 24 items, 11 fields filled in every item. price: 430 to 720, median 590; name: “GG Marmont reversible belt” and 15 other values.
MCP tool gucci_search
/gucci/suggestReturns Gucci's own search-box typeahead suggestions for a partial query. The current public suggestion source does not provide per-phrase result counts. Not product data -- pass a suggestion's query into gucci-search for results.
Response notes
- A genuinely empty result (no matching suggestions) returns a well-formed empty `suggestions` list, not an error. - Gucci's current public suggestion source returns phrases but no per-phrase result counts, so `result_count` is omitted.
Sampled 14 Oct 2026: 5 items, 1 field filled in every item. query: “belts” and 4 other values.
MCP tool gucci_suggest
/gucci/categoriesReturns Gucci's full department/category/subcategory taxonomy, sourced directly from the site's own header navigation menu. Each entry's category value is exactly what gucci-category's own category parameter accepts. Filter to one department with department (e.g. women, men); omit for every department -- see the response's own departments field for the live list of top-level department labels to filter by.
Response notes
- `departments` lists every top-level department the site's own navigation exposes (e.g. Women, Men, Children, Jewelry & Watches, Décor & Lifestyle, Fragrances & Make-Up, Gifts). - `path` is the full "Department > Group > Leaf" label breadcrumb as the site's own nav menu presents it. - Not every navigation link is a browsable category: editorial/campaign pages and the store locator are excluded, since `gucci-category` would reject them.
Sampled 14 Oct 2026: 4 of 4 fields returned with a value. country: “us”; departments: 13 entries.
MCP tool gucci_categories
/gucci/categoryReturns one Gucci category/browse listing: products (name, price, colors, images, stock) plus the upstream's own product count, page count, sibling-category counts, and sort options. category comes from gucci-categories' own category field. page selects how many of the upstream's own batches to accumulate -- Gucci's own category pages page this way: requesting page=N returns every product from page 1 through page N combined (its own "Load All" button simply requests the last page), not a single page's worth. Defaults to 1 (the upstream's own first batch, 36 products); request page equal to the response's own pages_count to fetch a category's complete listing in one call.
Response notes
- Gucci's own category pages page cumulatively: requesting `page=N` returns every product from page 1 through page N combined (its own "Load All" button on the site simply requests the last page), not a single page's worth. Request `page` equal to the response's own `pages_count` to fetch a category's complete listing in one call. - `facets` reports sibling/cross-cutting category counts within the current listing's context (e.g. a `new` or `gifts` shelf a product also belongs to), not only true subcategories of `category`. - `sort_options` lists every value the site's own sort control accepts (`default`, `newest`, `price-desc`, `price-asc`). - An unrecognized `category` value returns a not-found error.
Sampled 14 Oct 2026: 36 items, 11 fields filled in every item. price: 1,450 to 3,950, median 2,390; name: “Paparazzo large top handle bag” and 21 other values.
MCP tool gucci_category
/gucci/productReturns product detail for one style: name, price, images, stock, and PDP attributes available from Gucci's current storefront, including description, breadcrumbs, SKU, colors, materials, and sizes. style_code comes from gucci-search's or gucci-category's own style_code field. PDP-only fields are omitted if the detail page is unavailable.
Response notes
- The anonymous Product Discovery Catalog API resolves the style code to its current product page. JSON-LD supplies description, offer, and breadcrumbs; `__BUYAREA_PROPS__` supplies the sellable SKU, colors, materials, and sizes. Unavailable PDP-only fields are omitted without failing the catalog result. - `sizes`, `colors`, `materials`, and `sku` reflect the US storefront only. - `price` and `currency` are always in USD. - An unrecognized `style_code` returns a not-found error.
Sampled 14 Oct 2026: 18 of 18 fields returned with a value. price: 4,450; name: “Bamboo Tote large bag”.
MCP tool gucci_product
/gucci/size-guideReturns Gucci's own size-conversion chart for one product style, as a plain header row plus data rows. Not every style carries one -- a one-size accessory (a bag, a scarf) returns available: false with no headers/rows, a well-formed signal rather than an error. style_code comes from gucci-search's or gucci-category's own style_code field.
Response notes
- Not every style carries a size chart: a one-size accessory (a bag, a scarf) returns `available: false` with no `headers`/`rows`, a well-formed signal rather than an error. - `title` reflects the chart's own category label (e.g. `MEN'S SHOES`, `WOMEN'S RINGS`) -- the same chart is shared across every style in that category, not unique per style code. - `rows` mirrors the upstream chart's own column order exactly as `headers` lists it (e.g. size, IT/EU, UK/AU, US, foot length).
Sampled 14 Oct 2026: 5 of 5 fields returned with a value. title: “MEN'S SHOES”; available: true.
MCP tool gucci_size_guide
/gucci/recommendationsReturns one Gucci recommendations shelf: product summaries (name, price, image, stock) from either a given product's own "You May Also Like" carousel (style_code set) or the site's general trending-items shelf (style_code omitted). style_code comes from gucci-search's or gucci-category's own style_code field.
Response notes
- `model` reports which shelf the response came from: `related-products` (style_code given) or `trending-items` (style_code omitted). - `price` and `currency` are always in USD (the US storefront only). - A style code with no related-items shelf returns a well-formed empty `products` list, not an error.
Sampled 14 Oct 2026: 10 items, 8 fields filled in every item. price: 2,065 to 4,600, median 4,150; name: “Bamboo Tote large bag” and 8 other values.
MCP tool gucci_recommendations
/gucci/storeReturns one Gucci store's full detail: name, phone, address, opening hours, and photos. slug comes from gucci-stores' own slug field.
Response notes
- `opening_hours` is a list of day-range rules: `days` are open `opens`-`closes` (24h, local store time). - An unrecognized `slug` returns a not-found error.
Sampled 14 Oct 2026: 2 items, 3 fields filled in every item. opens: “10:00” and 1 other value; days: median 1 entry.
MCP tool gucci_store
/gucci/storesReturns Gucci's full US store-locator listing: name, address, phone, coordinates, product departments carried, and a link to book an in-store appointment for each location. Filter to stores carrying one department with department (e.g. jewelry, mens_shoes); omit for every store -- see the response's own departments field for the live list of department tags to filter by.
Response notes
- `slug` is the value `gucci-store`'s own `slug` parameter accepts, to fetch that store's opening hours. - `departments` (top level) lists every department tag present across the whole listing; each `store`'s own `departments` lists only the tags that location carries. - `book_appointment_url`, when present, opens that store's private-appointment booking flow.
Sampled 14 Oct 2026: 96 items, 9 fields filled in every item, 3 not. type: store (84), flagship (12); name: “Chicago Flagship” and 95 other values.
MCP tool gucci_stores
/gucci/stores/searchSearches Gucci's public store-map GeoJSON feed for locations inside the requested viewport. market selects the storefront locale and localized labels; it does not filter results by country. The supported, live-verified market values are ca (English), fr (French), jp (Japanese), uk (English), and us (English). Coordinates and viewport bounds determine the returned stores. The Gucci site's text field geocodes in the browser and its name parameter does not filter this feed, so callers must provide bounds and a center (geocode a place before calling). Dateline-crossing bounds are not supported.
Response notes
- `count` is the number of returned map features; a valid empty `features` array is returned as `count: 0`. - The upstream JSON body includes an internal `status` string that has been observed as `416` alongside valid HTTP 200 responses and real store features. The scraper uses the HTTP status and GeoJSON structure instead. - Names and text fields are localized according to `market`; geometry comes from the requested viewport and may include stores outside that locale's country. Example request: `GET /api/v1/gucci/stores/search?market=uk&north=51.691&west=-0.510&south=51.286&east=0.335&latitude=51.5072&longitude=-0.1276`
Sampled 14 Oct 2026: 16 items, 7 fields filled in every item. type: store (14), flagship (2); name: “London Bond Street Flagship” and 15 other values.
MCP tool gucci_store_search
Related 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.
How to scrape Gucci
Gucci's ten endpoints cover category and product discovery plus store locations. Category pages accumulate through the requested page number, while the store map feed is geographic: geocode a place yourself, then send a viewport and center. Its verified market subset currently includes ca, fr, jp, uk, and us; market localizes labels but does not constrain stores to that country.
Call /gucci/categories for Gucci's full department/category/subcategory taxonomy with breadcrumb paths, sourced from its own header nav. Pass a category value to /gucci/category — its page parameter accumulates: page=N returns every product from page 1 through N combined, mirroring the site's own "Load All" button, so request page equal to the response's own pages_count for a category's complete listing in one call.
Send q to /gucci/search for normalized product summaries with the search index's own live total_results and total_pages. page (default 1) and limit (default 24, max 100) control pagination; a nonsense query returns a well-formed empty list with total_results: 0 rather than an error.
Pass a style_code from a search or category result to /gucci/product for marketing description, breadcrumb trail, gender, colors, materials, sizes, sku, price, and separate in_stock_online/in_stock_stores flags. description falls back to a shorter variation description if the full product page could not be fetched, rather than failing outright.
Send q to /gucci/suggest for the storefront's own typeahead phrases, each carrying a live result_count. limit (default 5, max 20) caps how many come back; pass a suggestion straight into /gucci/search's q for product results.
Use /gucci/size-guide for the public sizing chart and /gucci/recommendations with a product style code for related items, keeping those merchandising signals alongside the product's own price and variant fields.
Call /gucci/stores to list public store features, or send bounds and a center to /gucci/stores/search. All six coordinates are required and the center must fall inside the viewport; the endpoint does not geocode place names.
On 2026-10-30 /gucci/search for belt reported total_results 180 over 8 pages of 24 with size facets, recommendations for style_code A005Y8AAG231096 returned 10 products, and /gucci/category answered 503 Gucci blocked the request.
Agent skills
Install a Crawlora agent skill and your agent can pull Gucci data as JSON through the documented API, without writing a scraper. These skills cover Gucci:
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
Gucci's own category pages accumulate rather than paginate independently — /gucci/category's page=N returns every product from page 1 through page N combined. Request page equal to the response's own pages_count field to get that category's complete listing in a single call, the same result its own site's "Load All" button produces.
It reports sibling and cross-cutting category counts within the current listing's context — for example how many of the current products also sit in a new or gifts shelf — not only true subcategories of the category you requested.
No — /gucci/search is relevance-ranked, and a genuinely non-matching query returns a well-formed empty products list with total_results: 0 rather than an error, so an empty result is a normal, valid response to check for.
No. Gucci's browser geocodes free-text locations before loading the map, but the map feed does not filter on its name parameter. Geocode the location separately and pass the resulting bounding box and center coordinates.
No. market selects the storefront locale and localized labels; geometry still comes from the requested viewport and may include stores outside that locale's country. The currently verified market values are ca, fr, jp, uk, and us.
No — /gucci/product and /gucci/search always return price and currency for the US storefront (USD), regardless of query parameters, since this endpoint family only scrapes the US site.
No — only your Crawlora API key. Gucci's category, search, product, and suggestion data are collected from its public, credential-free storefront surface.