Quince APIquince.com ↗
Search Quince's catalog, fetch product details (prices, colors, sizes, materials), and browse categories across women's, men's, and home with 3 endpoints.
What is the Quince API?
The Quince API provides 3 endpoints to search, browse, and retrieve detailed product data from quince.com. Use search_products to query the catalog by keyword, category, or gender filter. Use get_product_details to pull per-product fields including price, available sizes, hex-coded color variants, material details, and images. Use get_categories to navigate the full hierarchical category tree.
curl -X GET 'https://api.parse.bot/scraper/4a6489f8-f5db-4a6f-bb84-bb3916ce2887/search_products?page=1&limit=5&query=sweater&gender=Female&category=women%3Esweaters-jackets%3Ecashmere-sweaters' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace quince-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: Quince SDK — browse categories, search products, drill into details."""
from parse_apis.quince_product_api import Quince, Gender, GroupId, ProductNotFound
client = Quince()
# Browse top-level categories to discover what's available.
for cat in client.categories.list(group_id=GroupId.ALL, limit=5):
print(cat.name, cat.product_count)
# Search for cashmere sweaters in the women's category.
for item in client.productsummaries.search(query="sweater", gender=Gender.FEMALE, limit=3):
print(item.name, item.price, item.slug)
# Drill into the first search result for full details.
summary = client.productsummaries.search(query="cashmere", limit=1).first()
if summary:
product = summary.details()
print(product.title, product.price, product.variant_count)
for color in product.colors:
print(color.name, color.hex_code)
if product.review_summary:
print(product.review_summary.average_rating, product.review_summary.review_count)
# Fetch a known product directly by slug.
try:
detail = client.products.get(slug="women/cashmere/cashmere-crewneck-sweater")
print(detail.title, detail.price, detail.care_instructions)
except ProductNotFound as exc:
print(f"Product not found: {exc}")
print("exercised: categories.list / productsummaries.search / summary.details / products.get")
Full-text search over Quince product catalog. query matches product titles and descriptions; results can be narrowed by category group_id and gender. Returns lightweight product summaries with pricing and available filter facets. Paginates via page number. Each ProductSummary exposes a .details() drill-down (a separate fetch).
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination |
| limit | integer | Number of results per page (max 100) |
| query | string | Search keyword |
| gender | string | Gender filter: 'Female', 'Male', or 'Unisex' |
| category | string | Category group_id to filter by (e.g., 'women>dresses', 'women>cashmere'). Use get_categories to discover available group IDs. |
{
"type": "object",
"fields": {
"page": "integer - current page number",
"limit": "integer - results per page",
"query": "string - the search keyword used",
"products": "array of product summary objects with id, name, url, slug, price, image_url, description, group_ids",
"total_results": "integer - total number of matching products",
"available_filters": "object mapping filter names to arrays of available values"
}
}About the Quince API
What the API Covers
The Quince API gives programmatic access to the quince.com product catalog across women's, men's, and home categories. The three endpoints cover catalog search, individual product lookup, and category tree navigation. All endpoints return structured JSON with no authentication required on your end beyond your Parse key.
Search and Filtering
search_products accepts a query string plus optional gender ('Female', 'Male', or 'Unisex') and category filters. The category param takes a group_id string in the form women>dresses or women>cashmere — use get_categories first to enumerate valid values. Results include an available_filters object that maps filter names to their possible values for the current result set, making it straightforward to build faceted search interfaces. Pagination is controlled by page and limit (up to 100 per page), and total_results tells you how many records match.
Product Detail Fields
get_product_details accepts a product_id, slug, or full url — at least one is required. The response includes title, price, sizes (array of size strings), colors (array of objects with name and hex_code), details (materials and fabric description), and an images object that groups photos by color variant. The gender field on the product response reflects the target demographic as stored in the catalog.
Category Tree Navigation
get_categories takes an optional group_id parameter. Pass 'all' for top-level nodes, 'women' or 'm' for gender-specific subcategory trees. Each category object in the response includes group_id, name, product_count, and a children array for nested subcategories. This hierarchy is what you'd pass back into search_products as the category filter.
The Quince API is a managed, monitored endpoint for quince.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when quince.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official quince.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a price-tracking tool that monitors Quince product prices by product_id over time.
- Generate a size and color availability matrix for a specific product using the sizes and colors fields from get_product_details.
- Construct a faceted search UI using the available_filters object returned by search_products.
- Enumerate the full Quince category hierarchy with get_categories to map product taxonomy for a comparison shopping tool.
- Filter men's or women's products by category and keyword to populate a curated gift guide.
- Extract material and fabric details from the details field to tag and classify products by composition (e.g., cashmere, linen, cotton).
- Aggregate product counts per category using get_categories product_count fields to analyze catalog depth.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.