Get a Quince product API

Endpoint facts

Method

GET

API path

/quince/product

Auth

apiKey

Credits

3 credits/request

Platform

Quince

Response schema

#/definitions/quince.productResponseDoc

Overview

Returns normalized product-detail data for one Quince product: title, description, review summary, every selectable option (color swatches with hex codes, sizes), and every color/size variant with its own price, original ("traditional retail") price, stock status, and SKU. handle is the product's URL path on quince.com (for example women/cashmere/cashmere-crewneck-sweater), returned by quince-search's own products[].handle 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

- Unlike some other families' product-detail endpoints, one Quince product-detail response covers every color and size together (Quince's own PDP is not scoped to a single color variant per request). - Each `variants[]` entry's `options` is a flattened map of the option values that select that specific variant, e.g. `{"Color":"Ivory","Size":"XS"}`. - `variants[].in_stock` reflects Quince's own listing status for that variant (`ACTIVE`), not a real-time inventory count. - `options[].values[].hex_code` is only populated for color-swatch options. - An unknown `handle` returns `404`. - A malformed `handle` (not matching Quince's own URL-path shape) returns `400` before any upstream request is made. - `country` (top-level) and each variant's `currency` are always `US`/`USD` -- this endpoint only ever scrapes Quince's US storefront. Example response: ```json { "code": 200, "msg": "OK", "data": { "handle": "women/cashmere/cashmere-crewneck-sweater", "product_id": 76, "title": "Mongolian Cashmere Crewneck Sweater", "description": "The icon, now spring-ready. Our signature cashmere crew is luxuriously soft and surprisingly breathable.", "gender": "female", "product_type": "Crewneck", "average_rating": 4.87, "review_count": 34404, "country": "US", "options": [ { "name": "Color", "values": [ {"value": "Ivory", "display_name": "Ivory", "display_type": "Color", "hex_code": "#F5F0E6"}, {"value": "Heather Grey", "display_name": "Heather Grey", "display_type": "Color", "hex_code": "#808080"} ] }, { "name": "Size", "values": [ {"value": "XS", "display_name": "XS", "display_type": "Text"}, {"value": "S", "display_name": "S", "display_type": "Text"} ] } ], "variants": [ { "id": 3379, "sku": "LB19745", "title": "XS / Ivory", "price": 50, "traditional_retail_price": 148, "currency": "USD", "savings": "66%", "status": "ACTIVE", "in_stock": true, "options": {"Color": "Ivory", "Size": "XS"} } ], "images": [ "https://images.ctfassets.net/afruo3gr1g6h/img1/main.jpg" ], "url": "https://www.quince.com/women/cashmere/cashmere-crewneck-sweater" } } ```

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