Gucci product size chart API

Endpoint facts

Method

GET

API path

/gucci/size-guide

Auth

apiKey

Credits

3 credits/request

Platform

Gucci

Response schema

#/definitions/gucci.sizeGuideResponseDoc

Overview

Returns 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. 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

3 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

- 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). Example response: ```json { "code": 200, "msg": "OK", "data": { "style_code": "757892AACAG9055", "available": true, "title": "MEN'S SHOES", "headers": ["SIZE", "IT/EU", "UK/AU", "US", "KR(MM)", "JP(CM)", "MX", "FOOT LENGTH(INCH)"], "rows": [ ["4", "38", "4", "4.5", "230", "23", "4.5", "9.61"], ["4.5", "38.5", "4.5", "5", "235", "23.5", "5", "9.76"] ] } } ```

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