Beauty catalog and pricing monitoring
Use Kylie Cosmetics endpoints to turn beauty catalog and pricing monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Kylie Cosmetics's public Shopify storefront into structured retail data for makeup and beauty products — full product catalog and detail with every size and color variant, collection browsing, storefront pages, recommendations, and sitemap discovery, all pinned to Kylie Cosmetics's own storefront URL so no url parameter is needed. Credential-free.
Get Kylie Cosmetics products, collections, pages, and recommendations as structured JSON through a pinned endpoint family — no url parameter needed.
Endpoint families
6
Documented params
30
Examples
11
Live catalog snapshot
Active endpoints
11
Methods
GET
Required params
16
Schema refs
11
{
"platform": "Kylie Cosmetics",
"endpoint": "kyliecosmetics-store",
"method": "GET",
"path": "/kyliecosmetics/store",
"auth": "apiKey"
}Use cases
Get Kylie Cosmetics products, collections, pages, and recommendations as structured JSON through a pinned endpoint family — no url parameter needed.
Use Kylie Cosmetics endpoints to turn beauty catalog and pricing monitoring into repeatable API requests with documented inputs and JSON responses.
Use Kylie Cosmetics endpoints to turn collection and merchandising research into repeatable API requests with documented inputs and JSON responses.
Use Kylie Cosmetics endpoints to turn storefront page and sitemap discovery into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Kylie Cosmetics endpoint catalog — 11 endpoints, 30 documented request parameters, and 11 published response schemas — the same catalog Docs and Playground run against.
11 documented Kylie Cosmetics endpoints, grouped into 7 request families — Products, Collections and Pages, plus 4 more.
30 request parameters are documented across those Kylie Cosmetics endpoints, 16 of them required — the full input contract is public before you write any integration code.
11 of the 11 Kylie Cosmetics endpoints ship a recorded example response, and 11 carry a documented response schema — you can code against the real JSON before the first request.
Kylie Cosmetics endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
11 hosted MCP tools back the Kylie Cosmetics endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/kyliecosmetics/products
/kyliecosmetics/collections
/kyliecosmetics/pages
/kyliecosmetics/search/suggest
/kyliecosmetics/sitemap/urls
/kyliecosmetics/sitemaps
Endpoint catalog
/kyliecosmetics/storeReturns normalized storefront metadata for Kylie Cosmetics (https://www.kyliecosmetics.com), sourced from credential-free storefront JSON. This endpoint is a brand-pinned wrapper around the generic Shopify store family: the storefront URL is fixed server-side, so no `url` parameter is accepted. If the vanity domain blocks `/products.json`, the service may fall back to a public `*.myshopify.com` domain discovered from the storefront page, or to the storefront's own embedded page data for storefronts that expose neither.
Response notes
- Returns the resolved source URL used for JSON requests. - Includes `myshopify_domain`, store name, currency, country, and published product/collection counts when `/meta.json` exposes them. - Blocked pages, malformed JSON, missing Shopify roots, and unavailable fallback domains return upstream errors. - If the classic `/products.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the storefront's own pages directly and parsing their embedded structured data. When this fallback was used, `transport_mode` is `ssr_embedded`; it is omitted entirely for stores served by the classic catalog JSON. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP tool kyliecosmetics_store
/kyliecosmetics/productsReturns normalized products from Kylie Cosmetics's (https://www.kyliecosmetics.com) public product catalog. The storefront URL is fixed server-side. Valid empty result pages return `200` with an empty products array.
Response notes
- Valid empty result pages return `200` with an empty `products` array. - Product prices are normalized to decimal currency units. - Blocked pages, malformed JSON, and missing `products` roots return upstream errors. - If the classic `/products.json` endpoint and `*.myshopify.com` domain resolution are both unavailable (some headless storefronts on a Shopify catalog do not expose either), the service falls back to the storefront's own conventional "all products" collection page and parses its embedded search-result payload. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, `total_items`, and `total_pages`, plus additive per-product fields (`colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, per-variant `inventory_quantity`). `limit` is honored as an upper bound; the underlying page size is fixed by the storefront and cannot be requested larger in fallback mode. All of the above are omitted entirely for stores served by the classic catalog JSON. - When the `ssr_embedded` fallback was used, the response may also include `facets` and `facets_stats`, mirroring the storefront's own filter sidebar for that listing. - This brand-pinned endpoint does not accept `sortBy` or facet-filter query parameters (out of scope -- use the generic `/shopify/products` endpoint with `url` set to this brand's storefront for sort/filter support). The response reuses the same shared DTO as the generic family, which carries `sort`/`filters` fields for that feature; they are always omitted here since this endpoint never populates them. `sort` allowed values (never actually returned by this endpoint, listed for schema completeness): `sortLTH`, `sortHTL`, `newest`. This brand-pinned endpoint also does not accept the generic family's `sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`option_*` Storefront Filtering params (same out-of-scope reasoning -- use the generic `/shopify/products` endpoint with `url` set to this brand's storefront). The response DTO carries the matching `sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`variant_options` fields for that feature; they are always omitted here since this endpoint never populates them. `sort_by` allowed values (never actually returned by this endpoint, listed for schema completeness): `manual`, `best-selling`, `title-ascending`, `title-descending`, `price-ascending`, `price-descending`, `created-ascending`, `created-descending`. `transport_mode` allowed values: `ssr_embedded`, `storefront_filtered` (only ever these two values; omitted for the classic transport).
MCP tool kyliecosmetics_products
/kyliecosmetics/products/{handle}Returns normalized product detail for one Kylie Cosmetics (https://www.kyliecosmetics.com) product handle. The storefront URL is fixed server-side; `handle` is the product's URL slug.
Response notes
- Product prices from `.js` responses are normalized from cent values to decimal currency units. - Missing product handles return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing product fields return upstream errors. - If the classic product `.js` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the product detail page directly and parsing its embedded structured data (a richer Next.js data block when the storefront exposes one, otherwise the page's schema.org JSON-LD `ProductGroup`/`Product` block). When this fallback was used, the response includes `transport_mode: "ssr_embedded"` and additive fields (`colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, per-variant `inventory_quantity`). `transport_mode` is omitted entirely for stores served by the classic transport. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP tool kyliecosmetics_product
/kyliecosmetics/products/{handle}/recommendationsReturns normalized recommended products for one Kylie Cosmetics (https://www.kyliecosmetics.com) product handle. The route handle is resolved to a Shopify product id before fetching recommendations. The storefront URL is fixed server-side.
Response notes
- Missing product handles return `404` when Shopify returns not found while resolving the seed product. - Valid empty recommendation arrays return `200` with an empty `products` array. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - If the classic recommendations endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the seed product's own detail page (recommendations are embedded there). When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, with the same additive product fields documented for the products endpoint. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP tool kyliecosmetics_product_recommendations
/kyliecosmetics/collectionsReturns normalized collections from Kylie Cosmetics (https://www.kyliecosmetics.com). The storefront URL is fixed server-side. Valid empty result pages return `200` with an empty collections array.
Response notes
- Valid empty result pages return `200` with an empty `collections` array. - Blocked pages, malformed JSON, and missing `collections` roots return upstream errors. - If the classic `/collections.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to enumerating collections from the storefront's own `collections` sitemap. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, and `title` is a best-effort derivation from the handle -- **not** the storefront's real display name. `products_count` and other classic-only fields are omitted, never fabricated. - In fallback mode, `handle` is derived from the last path segment of the collection URL and is not guaranteed unique across nested sub-collections; use the item's own `url` to identify a specific one. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP tool kyliecosmetics_collections
/kyliecosmetics/collections/{handle}/productsReturns normalized products from one Kylie Cosmetics (https://www.kyliecosmetics.com) collection. The storefront URL is fixed server-side; `handle` is the collection's URL slug.
Response notes
- Valid empty result pages return `200` with an empty `products` array. - Missing collections return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing `products` roots return upstream errors. - If the classic collection `/products.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the collection listing page directly and parsing its embedded search-result payload. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, `total_items`, `total_pages`, plus additive per-product fields (`colour`, `canonical_colour`, `discount_percentage`, `rating`, `rating_count`, `collection_tags`, `labels`, per-variant `inventory_quantity`) and may include `facets`/`facets_stats`. `limit` is honored as an upper bound only; underlying page size is fixed by the storefront in fallback mode. - This brand-pinned endpoint does not accept `sortBy` or facet-filter query parameters (out of scope -- use the generic `/shopify/collections/{handle}/products` endpoint with `url` set to this brand's storefront for sort/filter support). The response reuses the same shared DTO as the generic family, which carries `sort`/`filters` fields for that feature; they are always omitted here since this endpoint never populates them. `sort` allowed values (never actually returned by this endpoint, listed for schema completeness): `sortLTH`, `sortHTL`, `newest`. This brand-pinned endpoint also does not accept the generic family's `sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`option_*` Storefront Filtering params (same out-of-scope reasoning -- use the generic `/shopify/collections/{handle}/products` endpoint with `url` set to this brand's storefront). The response DTO carries the matching `sort_by`/`min_price`/`max_price`/`product_type`/`in_stock_only`/`variant_options` fields for that feature; they are always omitted here since this endpoint never populates them. `sort_by` allowed values (never actually returned by this endpoint, listed for schema completeness): `manual`, `best-selling`, `title-ascending`, `title-descending`, `price-ascending`, `price-descending`, `created-ascending`, `created-descending`. `transport_mode` allowed values: `ssr_embedded`, `storefront_filtered` (only ever these two values; omitted for the classic transport).
MCP tool kyliecosmetics_collection_products
/kyliecosmetics/search/suggestReturns products, collections, and query suggestions from Kylie Cosmetics's (https://www.kyliecosmetics.com) credential-free predictive search Ajax endpoint. The storefront URL is fixed server-side.
Response notes
- Products and collections are normalized to the same shapes used by the product and collection endpoints. - Query suggestions include text and a storefront search URL when the storefront provides one. - Valid empty suggestion arrays return `200` with empty arrays. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors.
MCP tool kyliecosmetics_search_suggest
/kyliecosmetics/pagesReturns normalized static pages from Kylie Cosmetics (https://www.kyliecosmetics.com). The storefront URL is fixed server-side.
Response notes
- Page content is cleaned text from Shopify `body_html`; raw HTML is not returned. - Valid empty page arrays return `200` with an empty `pages` array. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - If the classic `/pages.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to enumerating page handles from the storefront's own `pages` sitemap. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`, and each item only carries `handle`, `url`, and `updated_at` -- no `title`, `id`, or `content`. Call the single-page endpoint per handle for full content. `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP tool kyliecosmetics_pages
/kyliecosmetics/pages/{handle}Returns normalized static page detail for one Kylie Cosmetics (https://www.kyliecosmetics.com) page handle. The storefront URL is fixed server-side.
Response notes
- Page content is cleaned text from Shopify `body_html`; raw HTML is not returned. - Missing page handles return `404` when Shopify returns not found. - Blocked pages, malformed JSON, and missing Shopify roots return upstream errors. - If the classic `/pages/{handle}.json` endpoint and `*.myshopify.com` domain resolution are both unavailable, the service falls back to fetching the page's own HTML and parsing an embedded Contentful CMS entry. When this fallback was used, the response includes `transport_mode: "ssr_embedded"`; `content` is plain text rendered from the page's rich-text blocks, and `id` is omitted (the source id is a Contentful entry id, not a Shopify numeric id). `transport_mode` allowed values: `ssr_embedded` (only ever present, never any other value; omitted for the classic transport).
MCP tool kyliecosmetics_page
/kyliecosmetics/sitemapsReturns child sitemap URLs from Kylie Cosmetics's (https://www.kyliecosmetics.com) `/sitemap.xml` index with inferred sitemap types. The storefront URL is fixed server-side.
Response notes
- Sitemap `type` is inferred from the child sitemap URL. - Inferred sitemap types are `products`, `collections`, `pages`, `blogs`, `agentic_discovery`, and `other`. - Blocked pages, malformed XML, and missing sitemap entries return upstream errors.
MCP tool kyliecosmetics_sitemaps
/kyliecosmetics/sitemap/urlsReturns capped URL entries from Kylie Cosmetics's (https://www.kyliecosmetics.com) child sitemaps matching the requested type. The storefront URL is fixed server-side.
Response notes
- The service fetches matching child sitemaps from `/sitemap.xml` until `limit` URL entries is reached. - URL entries include `loc`, inferred `type`, `handle`, `lastmod`, `changefreq`, and optional `images`. - Blocked pages, malformed XML, and missing sitemap entries return upstream errors.
MCP tool kyliecosmetics_sitemap_urls
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
Company coverage
Coty Inc. · COTY
Kylie Cosmetics is operated by Coty Inc. (COTY). Crawlora's SEC endpoints take the same company's CIK, so filings, financials, insider transactions and 13F holdings come from the same API key as the Kylie Cosmetics endpoints above.
SEC filings & financials API →How to scrape Kylie Cosmetics
Crawlora's Kylie Cosmetics endpoints return beauty catalog data as normalized JSON, pinned server-side to www.kyliecosmetics.com. One storefront carries several of Kylie Jenner's lines, and the vendor field tells them apart: kylie-cosmetics, kylie-fragrance, kylie-skin, kylie-samples, and kylie-baby. On 2026-09-18, /kyliecosmetics/store reported 249 published products and 228 collections.
All 249 products fit in one call to /kyliecosmetics/products at limit=250. Group on vendor: 160 were kylie-cosmetics, 51 kylie-fragrance, 26 kylie-samples, 10 kylie-skin, and 2 kylie-baby.
Most listings are bundles, not single products. 108 were typed Bundle, 30 Set, and 21 Sample, against a handful of Lip Kit, Lip Gloss, Mascara, and Brush entries. Filter product_type to Bundle or Set to track gift-set pricing, or exclude those types to analyze the single-product range.
Colour products put their options under shade (sometimes capitalized as Shade), and a foundation such as Power Plush Longwear Foundation has 40 shade variants. Normalize the option name before joining across products. Most bundles have a single Title variant.
/kyliecosmetics/sitemaps returns 109 sitemaps: the same products, pages, collections, and blogs set repeated for 26 market locales (en-ca, en-au, en-cr, and others) plus the root. Keep the root sitemaps when you enumerate URLs, and use the locale copies only when you need a specific market's URLs. /kyliecosmetics/pages includes a Complexion Shade Match Quiz and the Kylie Rewards pages.
FAQ
Yes. The brand-pinned endpoints don't take a vendor filter, but every product's vendor field names its line (kylie-skin, kylie-fragrance, and so on), so filter the /kyliecosmetics/products response yourself.
Call /kyliecosmetics/products/{handle}. Shade products return one variant per shade, with its own price and availability, under an option named shade or Shade.
The store publishes a copy of its sitemap set for each international market. The 109 sitemaps are 27 copies of the same four types plus an agentic_discovery file. Deduplicate by path to avoid crawling the same product many times.
/kyliecosmetics/* pins Kylie Cosmetics's own storefront URL (https://www.kyliecosmetics.com) server-side, so every call needs only your Crawlora API key — no url parameter. The same storefront is also reachable through /shopify/* by passing url=https://www.kyliecosmetics.com, which is the only way to reach this storefront's sort and filter options on /shopify/products and /shopify/collections/{handle}/products — those two parameters are not exposed on the brand-pinned routes.