Retail pricing and availability monitoring
H&Mエンドポイントを使えば、「Retail pricing and availability monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Turn H&M's own app-backend storefront data into structured retail data — keyword product search, category listing pages, and per-product detail with every color's live per-size price and stock plus real customer reviews, all as normalized JSON. Credential-free.
Search H&M products, browse category listings, and get full product detail — per-color pricing, live per-size stock, and customer reviews — as structured JSON.
エンドポイントファミリー
3
ドキュメント化されたパラメータ
12
サンプル数
0
ライブカタログスナップショット
稼働エンドポイント
3
メソッド
GET
必須パラメータ
6
スキーマ参照
3
{
"platform": "H&M",
"endpoint": "hm-search",
"method": "GET",
"path": "/hm/search",
"auth": "apiKey"
}ユースケース
Search H&M products, browse category listings, and get full product detail — per-color pricing, live per-size stock, and customer reviews — as structured JSON.
H&Mエンドポイントを使えば、「Retail pricing and availability monitoring」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
H&Mエンドポイントを使えば、「Category catalog and product research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
H&Mエンドポイントを使えば、「Review and rating tracking」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
各CrawloraプラットフォームAPIは、特定のデータサーフェスに合わせて設計されています。汎用的なfetchエンドポイントを公開する代わりに、エンドポイント固有のリクエストロジック、マネージドインフラ、パース、正規化、課金、そしてPlaygroundで検証済みのサンプルを組み合わせています。
対象プラットフォームとエンドポイントの種類に合わせてリクエスト挙動をチューニングしています。
対応エンドポイントはマネージドプロキシルーティングを利用でき、信頼性を高めながらインフラ運用の手間を減らせます。
JavaScriptレンダリングが必要な動的ページは、マネージドブラウザインスタンス経由で処理できます。
チャレンジページや利用不能な上流レスポンスを検知し、明確に通知します。
結果は生のHTMLではなく、ドキュメント化されたJSONで返されます。
本番統合の前に、DocsとPlaygroundから同じルートをテストできます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/hm/listing
/hm/product/{product_id}
/hm/search
エンドポイントカタログ
/hm/searchRuns a free-text keyword search against H&M's own app-backend search data and returns normalized products with pricing, images, colors, and per-size stock, plus search-quality metadata (a spelling-correction suggestion, related searches, and a content-filter flag). Unlike category browsing, an obscure or nonsense keyword returns a genuine empty result (zero products) rather than a fallback set. Pagination is page-based and real: requesting a page beyond the real last page returns a normal response with an empty products array rather than an error.
/hm/listingReturns one H&M category's product listing page: normalized products with pricing, images, colors, and per-size stock, sourced from H&M's own app-backend listing data. category_id is an H&M category slug (e.g. ladies_newarrivals_all, men_newarrivals_all, ladies_jeans) -- this build does not expose a category/nav-tree discovery endpoint, so category_id values are currently sourced from known H&M storefront paths rather than a lookup call. Pagination is page-based and real: requesting a page beyond the category's real last page returns a normal response with an empty products array rather than an error.
/hm/product/{product_id}Returns one H&M product's full detail: every purchasable color grouped with its own per-size price and live availability, plus an aggregate rating and real customer reviews (author label, date, body, and rating) when the product has any. This data is not available from hm-listing or hm-search, which only carry one representative price and a per-color stock count. product_id is the numeric id from a listing/search result's id field or its url field's productpage.<id>.html segment. An unrecognized product_id returns 404.
関連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.
H&Mのスクレイピング方法
Crawlora's H&M endpoints return search, category listings, and product detail as normalized JSON with one API key — no H&M account required.
Send a free-text keyword to /hm/search for paginated, normalized products with pricing, images, and per-color stock.
Pass a known category slug (e.g. ladies_jeans, men_newarrivals_all) to /hm/listing for that category's product listing — H&M doesn't publish a category/nav-tree lookup call, so category_id values come from known storefront paths, not a discovery endpoint.
Pass a product_id (a listing/search result's id, or the digits in a product page's productpage.<id>.html URL) to /hm/product/{product_id} for every color's real per-size price and live availability, plus customer reviews when the product has any.
FAQ
Pass a known category slug to Crawlora's /hm/listing endpoint — H&M doesn't expose a category/nav-tree discovery call, so category_id values (e.g. ladies_jeans, men_newarrivals_all) are sourced from known storefront paths rather than a lookup call.
Yes — unlike category browsing, /hm/search returns a genuine empty result (zero products) for an obscure or nonsense keyword, rather than falling back to a recommended set.
Yes — /hm/product/{product_id} returns every purchasable color grouped with its own real per-size price and live availability, plus an aggregate rating and customer reviews when the product has any. /hm/listing and /hm/search only carry one representative price and a per-color stock count.