Sephora reference
Every Sephora operation, from the registry
12 operations wired in the registry, 12 of them proven by real traffic.
Choose a Sephora operation
Start with the object your task needs. The groups below use the current catalogue; open an endpoint to check accepted identifiers, filters, price and availability before retrieving.
Other operations
- Sephora store availability — Which stores near a point stock one sku, with distance and in-store availability.
- Sephora brands — Every brand the storefront lists, with ids and URLs.
- Sephora similar products — Products the storefront recommends alongside one product.
- Sephora stores near a point — Stores near a point with address, phone, hours, pickup and curbside flags.
Products and categories
- Sephora brand products — Products of one brand, sixty per page.
- Sephora categories — The storefront's top-level categories with ids for sephora/category.
- Sephora category products — Products in a category, sixty per page.
- Sephora category children — The child categories of one category.
- Sephora product — One product: brand, price, rating and review count, loves, description, usage, images and its shade or size variants.
Reviews and offers
- Sephora product reviews — Reviews of a product with author, rating, recommendation, verified-purchase badge, photos and helpfulness votes.
Search and discovery
- Sephora product search — Products matching a keyword, sixty per page, with brand, price, rating and badges.
- Sephora search suggestions — Search suggestions for a partial query, with the product each one leads to and the trending categories.
Check fields and collection limits
Use the endpoint’s declared parameters and returned continuation. Filters from another platform do not automatically apply here. Preserve source identifiers, URLs and warnings; a successful page does not establish complete history. Published response schemas identify whether they come from a reviewed shaper or observed response shapes.
Agents can use get_endpoint for the current contract and get_docs with topic platforms/sephora to read this page. The coverage guide explains nulls and partial results, and the production guide covers budgets and recovery.
Operations
Sephora
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Sephora
12 operationsElsewhere
The same registry, other shapes
- Sephora overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=sephora— the same rows to your code at runtime, for 0 credits.