Shapewear and loungewear catalog monitoring
SKIMSエンドポイントを使えば、「Shapewear and loungewear catalog monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn SKIMS's public Shopify storefront into structured retail data for shapewear, loungewear, and intimates — full product catalog and detail with every size and color variant, collection browsing, storefront pages, recommendations, and sitemap discovery, all pinned to SKIMS's own storefront URL so no url parameter is needed. Credential-free.
Get SKIMS products, collections, pages, and recommendations as structured JSON through a pinned endpoint family — no url parameter needed.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
30
サンプル数
11
ライブカタログスナップショット
稼働エンドポイント
11
メソッド
GET
必須パラメータ
16
スキーマ参照
11
{
"platform": "SKIMS",
"endpoint": "skims-store",
"method": "GET",
"path": "/skims/store",
"auth": "apiKey"
}ユースケース
Get SKIMS products, collections, pages, and recommendations as structured JSON through a pinned endpoint family — no url parameter needed.
SKIMSエンドポイントを使えば、「Shapewear and loungewear catalog monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
SKIMSエンドポイントを使えば、「Collection and merchandising research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
SKIMSエンドポイントを使えば、「Storefront page and sitemap discovery」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のSKIMSエンドポイントカタログから取得しています(エンドポイント11件、ドキュメント化されたリクエストパラメータ30個、公開レスポンススキーマ11件)。DocsとPlaygroundが参照しているカタログと同じものです。
SKIMSのエンドポイントは11件、7つのリクエストファミリーに分類されています(Products、Collections、Pagesほか4件)。
これらのSKIMSエンドポイントには30個のリクエストパラメータがドキュメント化されており、うち16個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
11件のSKIMSエンドポイントのうち11件が実際のサンプルレスポンスを、11件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
SKIMSのエンドポイントは成功時のスキーマに加えてエラーレスポンス(400、404、429、503)もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
SKIMSのエンドポイントは11個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/skims/products
/skims/collections
/skims/pages
/skims/search/suggest
/skims/sitemap/urls
/skims/sitemaps
エンドポイントカタログ
/skims/storeReturns normalized storefront metadata for SKIMS (https://skims.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.
レスポンスに関する注記
- 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ツール skims_store
/skims/productsReturns normalized products from SKIMS's (https://skims.com) public product catalog. The storefront URL is fixed server-side. Valid empty result pages return `200` with an empty products array.
レスポンスに関する注記
- 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ツール skims_products
/skims/products/{handle}Returns normalized product detail for one SKIMS (https://skims.com) product handle. The storefront URL is fixed server-side; `handle` is the product's URL slug.
レスポンスに関する注記
- 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ツール skims_product
/skims/products/{handle}/recommendationsReturns normalized recommended products for one SKIMS (https://skims.com) product handle. The route handle is resolved to a Shopify product id before fetching recommendations. The storefront URL is fixed server-side.
レスポンスに関する注記
- 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ツール skims_product_recommendations
/skims/collectionsReturns normalized collections from SKIMS (https://skims.com). The storefront URL is fixed server-side. Valid empty result pages return `200` with an empty collections array.
レスポンスに関する注記
- 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ツール skims_collections
/skims/collections/{handle}/productsReturns normalized products from one SKIMS (https://skims.com) collection. The storefront URL is fixed server-side; `handle` is the collection's URL slug.
レスポンスに関する注記
- 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ツール skims_collection_products
/skims/search/suggestReturns products, collections, and query suggestions from SKIMS's (https://skims.com) credential-free predictive search Ajax endpoint. The storefront URL is fixed server-side.
レスポンスに関する注記
- 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ツール skims_search_suggest
/skims/pagesReturns normalized static pages from SKIMS (https://skims.com). The storefront URL is fixed server-side.
レスポンスに関する注記
- 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ツール skims_pages
/skims/pages/{handle}Returns normalized static page detail for one SKIMS (https://skims.com) page handle. The storefront URL is fixed server-side.
レスポンスに関する注記
- 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ツール skims_page
/skims/sitemapsReturns child sitemap URLs from SKIMS's (https://skims.com) `/sitemap.xml` index with inferred sitemap types. The storefront URL is fixed server-side.
レスポンスに関する注記
- 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ツール skims_sitemaps
/skims/sitemap/urlsReturns capped URL entries from SKIMS's (https://skims.com) child sitemaps matching the requested type. The storefront URL is fixed server-side.
レスポンスに関する注記
- 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ツール skims_sitemap_urls
関連API
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.
SKIMSのスクレイピング方法
Crawlora's SKIMS endpoints return shapewear, loungewear, and underwear catalog data as normalized JSON, pinned to skims.com. SKIMS blocks Shopify's catalog JSON on its vanity domain, so requests are served from its skimsbody.myshopify.com backend. That is why /skims/store returns the domain mapping but no store name or counts. Its vendor field is unusual: it holds the fabric or product line (COTTON FLEECE, FITS EVERYBODY, NikeSKIMS ACCESSORIES) rather than the brand.
/skims/store reports no product count, so page /skims/products at limit=250 until products comes back empty. Titles are uppercase STYLE | COLOUR, as in COTTON FLEECE JOGGER WITH EMBOSSED LOGO | ONYX, with each colourway listed as its own product.
Group on vendor to split SKIMS lines. The first 500 products included COTTON FLEECE, COTTON JERSEY, FITS EVERYBODY, and the NikeSKIMS co-brand lines (ACCESSORIES, SATIN SHINE, STRETCH KNIT). product_type gives the garment class: TOPS, BOTTOMS, ACTIVE TOPS, PANTIES, BRAS, and so on.
Beyond Color and Size, bras carry Band Size and Cup Size options, and men's underwear and some active bottoms carry Inseam. A single bra can have 62 variants. Prices ran from $14 to $268 (median $64) in the first 500. Only one of those products showed a markdown, so SKIMS rarely uses compare_at_price.
/skims/collections has Color Spotlight edits, Best Selling Shapewear, and Best of NikeSKIMS. /skims/sitemaps is the largest set in this family, 1,282 sitemaps covering 182 market locales plus the root, so keep the root set. /skims/search/suggest for black returns NikeSKIMS footwear and SKIMS colour names like ONYX and SOOT, with completions such as blue black.
FAQ
SKIMS serves its catalog through skimsbody.myshopify.com instead of skims.com, and that route doesn't expose the metadata file the counts come from. The response still reports source_url and myshopify_domain.
Yes. Filter /skims/products on vendor names that start with NikeSKIMS, such as NikeSKIMS ACCESSORIES or NikeSKIMS SATIN SHINE, or use the Best of NikeSKIMS collection.
Yes. Bra products return Band Size and Cup Size options, and /skims/products/{handle} lists every band, cup, and colour combination as its own variant.
/skims/* pins SKIMS's own storefront URL (https://skims.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://skims.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.