H&M Category Navigation API

Endpoint facts

Method

GET

API path

/hm/categories

Auth

apiKey

Credits

5 credits/request

Platform

H&M

Response schema

#/definitions/hm.categoriesResponseDoc

Overview

Returns H&M's own storefront category navigation, department by department: every direct nav item and subcategory currently shown in the site's own menu, with its display name and storefront URL. Where this build has separately verified the value against hm-listing's own category_id parameter, that id is included too; category_id is omitted for entries not yet verified rather than guessed, since the visible category label is confirmed NOT a reliable way to derive H&M's real listing category ids for every category. department, when given, filters the result to one department. 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.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

5 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- Each entry's `section` is the nav group it lives under (e.g. `"Clothing"`, `"Accessories"`, `"Shoes"`), and is empty for a department's own direct nav item (e.g. `"New in"`). - `category_id`, when present, is the value to pass as `hm-listing`'s own `category_id` query parameter. It is included only where separately verified against `hm-listing`'s upstream, and is omitted -- not guessed -- for every other live nav entry, since the visible category label is confirmed not to reliably derive H&M's real listing category id for every category (for example, "T-shirts & Tops" resolves to `men_tshirtstanks`, not a slug built from the label). - Nav depth genuinely differs by department: Women and Men are two levels deep (department > group > leaf), Home and Beauty are one level deep (department > leaf directly), and Kids is deeper still (department > age/gender group > age-band group > leaf). A group node that is itself a real, directly browsable page (for example Kids's "2-8 years") appears both as its own entry and as the `section` for its own children. - The navigation itself reflects H&M's live site on every request; only the `category_id` enrichment is a periodically-refreshed reference table, so a brand-new category may appear with a name and URL before its `category_id` has been separately verified. - `source_url` reflects which of two upstream sources actually served the request: H&M's own credential-free Android-app navigation feed (`source_url` starting `https://app2.hm.com/...`), tried first, or the www2.hm.com web storefront's own shared header nav (`source_url` starting `https://www2.hm.com/...`), used as a fallback only if the app feed is unavailable. Both sources are kept in sync with the live site and produce the same response shape. ```json {"code":200,"msg":"OK","data":{"source_url":"https://app2.hm.com/content/hmonline/en_us/apis/navigation/v5/nav-data.json","fetched_at":"2026-08-15T08:00:00Z","categories":[{"department":"women","section":"","name":"New in","url":"https://www2.hm.com/en_us/ladies/new-arrivals.html"},{"department":"women","section":"Clothing","name":"Dresses","url":"https://www2.hm.com/en_us/ladies/shop-by-product/dresses.html","category_id":"ladies_dresses"}]}} ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related