API Reference
Use Crawlora's Sephora API endpoints to extract supported public Sephora data as structured JSON. This documentation covers 7 active endpoints including Sephora category browse, Sephora product detail, Sephora product questions and answers, Sephora product reviews, and related APIs. Developers can use these endpoints for monitoring, enrichment, research dashboards, internal data pipelines, and agent-native workflows without maintaining platform-specific scraping code. Each endpoint page documents authentication, request parameters such as slug, product_id, query, latitude, cURL examples, response examples, response schemas, errors, credit cost, and Playground testing. Send requests to the Crawlora API with an x-api-key header, review usage and plan limits on pricing, and test safe sample requests in Playground before moving the workflow into production.
Choose an endpoint, send an authenticated request with the x-api-key header, and inspect the normalized JSON response. The examples below use the public Crawlora API base URL and the same endpoint catalog used by Playground.
curl -X GET "https://api.crawlora.net/api/v1/sephora/search?query=coffee&page=1&sort_by=featured&is_new=true" \
-H "x-api-key: $CRAWLORA_API_KEY"These endpoint cards are generated from the active Crawlora endpoint catalog, including method, path, auth mode, credit cost, parameter summary, docs, and Playground links.
/sephora/categoryapiKey5 credits/requestReturns one page of a Sephora category/browse listing (e.g. Makeup, Skincare), with the same sort and facet filters as /sephora/search. slug is the path segment after sephora.com/shop/, e.g. makeup-cosmetics. The response uses Sephora's public catalog search to keep browse listings available when the category page's legacy embedded data is absent.
Required params: slug:query
/sephora/productapiKey3 credits/requestReturns one Sephora product's full detail (every color/shade variant with its own price and availability, rating, review count, and a sample of recent reviews), from Sephora's credential-free public JSON-LD. `product_id` is the full product-page slug, e.g. `lip-sleeping-mask-P420652` -- copy it from the path segment after sephora.com/product/ on any product page; unlike some other retailers, an arbitrary or partial slug does not resolve.
Required params: product_id:query
/sephora/product/questionsapiKey3 credits/requestReturns one page of a Sephora product's customer Q&A: each question plus every answer it received (text, author, whether it's a brand answer, helpful votes). product_id is the Sephora productGroupID, e.g. P420652 -- the same value /sephora/product returns as product_group_id.
Required params: product_id:query
/sephora/product/reviewsapiKey3 credits/requestReturns one page of a Sephora product's full customer reviews (title, body, rating, author, helpful votes, secondary ratings, photos), plus the product's site-wide rating rollup (average rating, recommended ratio, star-count histogram). product_id is the Sephora productGroupID, e.g. P420652 -- the same value /sephora/product returns as product_group_id.
Required params: product_id:query
/sephora/searchapiKey3 credits/requestSearches Sephora's product catalog by keyword, with real page-based pagination. Returns normalized products with brand, pricing, rating, and review count. Sephora's own search never returns a genuine zero-result state for a nonempty keyword -- an unrecognized/nonsense keyword still returns a full, unrelated fallback result set rather than an empty one. price_min/price_max must be provided together (whole dollars) -- upstream silently ignores a one-sided price range rather than filtering or erroring, so this endpoint rejects a one-sided range as invalid instead of passing it through. brand and filter each accept multiple values (OR'd together within the same facet); brand/rating_min/is_new/filter/price_min/price_max can all be combined with each other (AND'd together across different facets).
Required params: query:query
/sephora/storesapiKey5 credits/requestReturns Sephora physical store locations near a coordinate (address, hours, BOPIS/curbside/same-day flags). Renders through a JS-executing browser backend, unlike every other Sephora endpoint -- the store-locator data call itself is plain HTTP, but it requires a per-visit access token minted by an endpoint gated behind a bot-management JS challenge, so responses may take longer.
Required params: latitude:query, longitude:query
/sephora/suggestapiKey3 credits/requestReturns Sephora's own search-box type-ahead suggestions for a partial keyword: keyword-completion terms, matching products, and trending/related categories. Sephora's own upstream never returns a genuine zero-result state for a nonempty query -- a deliberately nonsense query still returns unrelated product suggestions.
Required params: query:query
| Endpoint | API path | Method | Credits | Required params | Docs | Playground |
|---|---|---|---|---|---|---|
| Sephora category browse | /sephora/category | GET | 5 credits/request | slug:query | View docs | Try endpoint |
| Sephora product detail | /sephora/product | GET | 3 credits/request | product_id:query | View docs | Try endpoint |
| Sephora product questions and answers | /sephora/product/questions | GET | 3 credits/request | product_id:query | View docs | Try endpoint |
| Sephora product reviews | /sephora/product/reviews | GET | 3 credits/request | product_id:query | View docs | Try endpoint |
| Sephora product search | /sephora/search | GET | 3 credits/request | query:query | View docs | Try endpoint |
| Sephora store locator | /sephora/stores | GET | 5 credits/request | latitude:query, longitude:query | View docs | Try endpoint |
| Sephora search suggestions | /sephora/suggest | GET | 3 credits/request | query:query | View docs | Try endpoint |