Get H&M search-box suggestions API

Endpoint facts

Method

GET

API path

/hm/search/suggestions

Auth

apiKey

Credits

3 credits/request

Platform

H&M

Response schema

#/definitions/hm.suggestResponseDoc

Overview

Returns H&M's own search-box typeahead suggestions, sourced from the same credential-free app-backend host as hm-listing/hm-search. When query is given, returns spelling-complete phrase suggestions and merchandised content results. When query is omitted or empty, instead returns trending searches and popular-search shortcuts (phrase/content suggestions are both empty in that mode). search_history is part of the real upstream response but confirmed NOT session-scoped -- it returned the identical list across separate cookie-free requests, so treat it as fixed default content rather than a real per-caller history. 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

3 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

- With `query` given, the response carries `phrase_suggestions` (spelling-complete phrases) and `content_suggestions` (merchandised results). `trending_searches` and `popular_searches` are both empty in this mode. - With `query` omitted or empty, the response instead carries `trending_searches` and `popular_searches`. `phrase_suggestions` and `content_suggestions` are both empty in this mode. - `search_history` is part of the real upstream response but confirmed NOT session-scoped: separate cookie-free requests returned the identical list, so treat it as fixed default content, not a real per-caller search history, despite the field name. - `blocked` mirrors the same content-filter flag `hm-search`'s own `search_meta.blocked` documents; its exact trigger conditions are not documented by H&M. - `content_suggestions[]`/`popular_searches[]` entries do not all carry every field -- `link`, `deep_link`, `image_url`, and `content_type` are each populated only when H&M's own response includes them. ```json {"code":200,"msg":"OK","data":{"query":"jean","phrase_suggestions":["jeans","jeans women","jeans men","jean shorts","jeans girls"],"blocked":false,"source_url":"https://api.hm.com/search-services/v1/en_us/search/suggestions?query=jean...","fetched_at":"2026-08-15T06:37:00Z"}} ``` ```json {"code":200,"msg":"OK","data":{"query":"","trending_searches":["back to school","sweatpants","shorts","dress","socks"],"popular_searches":[{"title":"Back to school "},{"title":"Spiderman","deep_link":"/content/hmonline/en_us/kids/seasonal-trending/character/boys","link":"/en_us/kids/seasonal-trending/character/character-youngboy.html"}],"search_history":["jeans","shirt","t-shirt"],"blocked":false,"source_url":"https://api.hm.com/search-services/v1/en_us/search/suggestions?query=...","fetched_at":"2026-08-15T06:37:00Z"}} ```

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