Get a Gucci product API

Endpoint facts

Method

GET

API path

/gucci/product

Auth

apiKey

Credits

2 credits/request

Platform

Gucci

Response schema

#/definitions/gucci.productResponseDoc

Overview

Returns full normalized product detail for one style: name, marketing description, breadcrumb trail, brand line, gender, colors, materials, sizes, price, images, and stock -- combining Gucci's own structured product record with the product page's own marketing copy. style_code comes from gucci-search's or gucci-category's own style_code field. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

2 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- `description` prefers the product page's own long-form marketing copy; if that page could not be fetched, it falls back to a shorter variation description instead of failing the whole request. - `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. Example response: ```json { "code": 200, "msg": "OK", "data": { "style_code": "A005Y8AAG231096", "name": "Bamboo Tote large bag", "description": "Gucci Primavera establishes a new vocabulary of silhouettes, textures, and materials...", "gender": "Women", "colors": ["#000000|Black"], "materials": ["Leather"], "sizes": ["U"], "sku": "814374772", "price": 4450, "currency": "USD", "availability": "InStock", "breadcrumbs": ["Women", "Handbags", "Shoulder Bags for Women"], "in_stock": true, "in_stock_online": true, "in_stock_stores": true, "url": "https://www.gucci.com/us/en/pr/women/handbags/shoulder-bags-for-women/bamboo-tote-large-bag-p-A005Y8AAG231096" } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related