J.Crew Search API

Endpoint facts

Method

GET

API path

/jcrew/search

Auth

apiKey

Credits

3 credits/request

Platform

J.Crew

Response schema

#/definitions/jcrew.searchResponseDoc

Overview

Searches the product catalog for either storefront (select with site, default jcrew). Returns normalized product summaries with USD pricing, gender, and a description, plus the search index's own facets (gender, fabric, category, size, color, price range, and others) with live per-option counts. sort selects relevance (default), price_asc, or price_desc. filter narrows results by one or more facet name:value pairs (comma-separated, e.g. productGender:Men,styleFabric:Cashmere) taken from a prior response's own facets[].name/facets[].options[].value fields -- not curated against a fixed list, since the facet set is large and can change. This is best-effort relevance, not a guaranteed keyword match: for an obscure alphanumeric keyword the upstream search index falls back to its own semantically-related results instead of an empty list, and there is no reliable field in the response to distinguish a true keyword match from that fallback. 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

- This search is best-effort relevance, not a guaranteed keyword match. For an obscure alphanumeric keyword, the upstream search index falls back to its own semantically-related results (Constructor.io's own "embeddings match" fallback) instead of an empty list, and there is no reliable field in the response to distinguish a true keyword match from that fallback. A genuine empty result was only reproduced with a symbols-only query. - `total_products` and `total_pages` reflect the upstream's own result count for the current `keyword`/`site`/`filter` combination. - Each product's `id` is the value to pass as `pid` to `jcrew-product-reviews`, `jcrew-product`, or `jcrew-size-chart` (with the same `site`). - `price_min`/`price_max` and `sale_price_min`/`sale_price_max` are USD, aggregated across every fit the style is offered in. - `facets` lists the search index's own available filters (gender, fabric, category, size, color, price range, and others) with live per-option result counts. A range facet (only `price` observed) sets `is_range` true and carries `range_min`/`range_max` instead of `options`. - `site=factory` uses J.Crew Factory's own independent search index (Constructor.io key, separate from the flagship site) -- results, facets, and product ids are entirely separate from `site=jcrew`. Example response: ```json {"code":200,"msg":"OK","data":{"keyword":"sweater","site":"jcrew","sort":"relevance","page":1,"per_page":24,"total_pages":15,"total_products":338,"count":1,"products":[{"id":"CX415","family_id":"ME617","name":"2025 Rollneck sweater","description":"A J.Crew icon since the '80s, refreshed for right now...","gender":"Women","image_url":"http://www.jcrew.com/s7-img-facade/CX415_NA6434?fmt=jpeg&qlt=90,0","orderable":true,"price_min":98,"price_max":128,"sale_price_min":98,"sale_price_max":98,"url":"https://www.jcrew.com/p/CX415"}],"facets":[{"name":"productGender","label":"Gender","type":"multiple","options":[{"label":"Women","value":"Women","count":208}]},{"name":"price","label":"Price","type":"range","is_range":true,"range_min":28,"range_max":429.99}]}} ```

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