H&M API endpoint
Use Crawlora's H&M Category Listing API to extract supported public H&M data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.
/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. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.
Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| category_id | string | Yes | H&M category slug | ||
| page | integer | No | 1 | Page number, one-based, defaults to 1 | |
| page_size | integer | No | 36 | Results per page, 1 to 72, defaults to 36 | |
| sort | string | No | RELEVANCE | Sort order, defaults to RELEVANCE Allowed values: RELEVANCE, NEWEST_FIRST, PRICE_ASCENDING, PRICE_DESCENDING | |
| is_new | boolean | No | Optional filter for newly added items only | ||
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/hm/listing?page=1&sort=RELEVANCE&is_new=true" \ -H "x-api-key: $CRAWLORA_API_KEY"
Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.
Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.
| Plan | Price | Included credits | Daily cap | Rate limit | Overage |
|---|---|---|---|---|---|
| Free | $0/mo | 2,000 | 500 daily credits | 5/min | No overage |
| Starter | $9/mo | 20,000 | 5,000 daily credits | 15/min | $0.75/1,000 overage credits when enabled |
| Growth | $29/mo | 100,000 | 25,000 daily credits | 45/min | $0.45/1,000 overage credits when enabled |
| Pro | $79/mo | 400,000 | No daily cap | 120/min | $0.30/1,000 overage credits |
| Business | $199/mo | 1,200,000 | No daily cap | 300/min | $0.20/1,000 overage credits |
| Enterprise | $499/mo | 5,000,000 | No daily cap | 1,000/min | $0.12/1,000 overage credits |
This endpoint is executed through Crawlora's managed scraping infrastructure.
- Pagination is real and page-based: the same `page` returns identical results on repeat requests, and different pages return different, non-overlapping products. - Requesting a `page` beyond the category's real last page returns a normal `200` with an empty `products` array. `total_pages` and `total_hits` stay at their real, nonzero values in that case, distinguishing it from `category_id` pointing at an invalid or empty category, where both are genuinely `0`. - `products[].id` can carry a leading zero, so it is returned as a string, not a number. - `products[].colors[]` lists every purchasable color for that product's own listing entry, each with its own image and product-page URL. - `products[].sizes[]` lists every size H&M's listing offers for the displayed color, each with its own live stock count. ```json {"code":200,"msg":"OK","data":{"category_id":"ladies_jeans","page":1,"page_size":2,"sort":"RELEVANCE","total_pages":195,"total_hits":585,"count":2,"source_url":"https://api.hm.com/search-services/v1/en_us/listing/resultpage?categoryId=ladies_jeans...","fetched_at":"2026-08-10T06:00:00Z","products":[{"id":"1045459086","name":"Harper High Rise Wide Leg Jeans","brand":"H&M","url":"https://www2.hm.com/en_us/productpage.1045459086.html","image_url":"https://image.hm.com/assets/hm/d9/cb/d9cbd5615ab3ae695b2ffee69245ef11a800d424.jpg","price":34.99,"formatted_price":"$34.99","currency":"USD","availability":"Available","new_arrival":false,"category_code":"ladies_jeans_wide","colors":[{"article_id":"1045459086","name":"Dark brown","color_code":"54443D","url":"https://www2.hm.com/en_us/productpage.1045459086.html","image_url":"https://image.hm.com/assets/hm/d9/cb/d9cbd5615ab3ae695b2ffee69245ef11a800d424.jpg"}],"sizes":[{"id":"003","label":"4","stock":2}]}]}} ```
Crawlora does not silently return bad data when the upstream page cannot be used.
| Status | Common failure case |
|---|---|
| 400 | Invalid input or missing required parameter |
| 429 | Plan or endpoint rate limit exceeded |
| 500 | Internal execution error |
| 502 | Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved |
When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Request schema
No body schema
Response schema
#/definitions/hm.listingResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| code | integer | No | 200 | |||
| data | hm.ListingResponse | No | ||||
| data.category_id | string | No | ||||
| data.count | integer | No | ||||
| data.fetched_at | string | No | ||||
| data.is_new | boolean | No | ||||
| data.page | integer | No | ||||
| data.page_size | integer | No | ||||
| data.products | array | No | ||||
| data.products[].availability | string | No | ||||
| data.products[].brand | string | No | ||||
| data.products[].category_code | string | No | ||||
| data.products[].colors | array | No | ||||
| data.products[].colors[].article_id | string | No | ||||
| data.products[].colors[].color_code | string | No | ||||
| data.products[].colors[].image_url | string | No | ||||
| data.products[].colors[].name | string | No | ||||
| data.products[].colors[].url | string | No | ||||
| data.products[].coming_soon | boolean | No | ||||
| data.products[].currency | string | No | ||||
| data.products[].formatted_price | string | No | ||||
| data.products[].id | string | No | ||||
| data.products[].image_url | string | No | ||||
| data.products[].model_image_url | string | No | ||||
| data.products[].name | string | No | ||||
| data.products[].new_arrival | boolean | No | ||||
| data.products[].price | number | No | ||||
| data.products[].sizes | array | No | ||||
| data.products[].sizes[].id | string | No | ||||
| data.products[].sizes[].label | string | No | ||||
| data.products[].sizes[].stock | integer | No | ||||
| data.products[].url | string | No | ||||
| data.sort | string | No | ||||
| data.source_url | string | No | ||||
| data.total_hits | integer | No | ||||
| data.total_pages | integer | No | ||||
| msg | string | No | OK |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/hm/listing?page=1&sort=RELEVANCE&is_new=true" \
-H "x-api-key: $CRAWLORA_API_KEY"Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.
Read Crawlora terms