H&M reference
Every H&M operation, from the registry
9 operations wired in the registry, 9 of them proven by real traffic.
Choose a H&M operation
Start with the object your task needs. The groups below use the current catalogue; open an endpoint to check accepted identifiers, filters, price and availability before retrieving.
Products and categories
- H&M categories — The category tree of an H&M storefront.
- H&M product — One H&M product: title, price, description, composition, care, colours and variants.
- H&M product suppliers — The supplier and factory record the retailer publishes for a product: country, supplier and each factory's name, address and workforce band.
Other operations
- H&M storefronts — The retailer's country and language list, by region, with each country's storefront language links.
- H&M new arrivals — The newest products on an H&M storefront.
- H&M similar products — Products similar to one product.
- H&M stores — Every store in a country: address, coordinates, opening hours, departments and status.
Search and discovery
- H&M product search — Products matching a keyword on an H&M storefront, with price, colours and images.
- H&M search suggestions — Search suggestions for a partial query.
Check fields and collection limits
Use the endpoint’s declared parameters and returned continuation. Filters from another platform do not automatically apply here. Preserve source identifiers, URLs and warnings; a successful page does not establish complete history. Published response schemas identify whether they come from a reviewed shaper or observed response shapes.
Agents can use get_endpoint for the current contract and get_docs with topic platforms/hm to read this page. The coverage guide explains nulls and partial results, and the production guide covers budgets and recovery.
Operations
H&M
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
H&M
9 operationsElsewhere
The same registry, other shapes
- H&M overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=hm— the same rows to your code at runtime, for 0 credits.