H&M Product Reviews API
Every review of an H&M product, across its colours and sizes, with ratings and fit.
GET /v1/hm/products/{id}/reviews3 credits Failed requests are free
About this endpoint
GET /v1/hm/products/{id}/reviews returns data.reviews[], data.totalResults, data.stats and data.page. A review carries id, rating, title, text, submittedAt, purchasedAt, helpfulCount, notHelpfulCount, isIncentivized, locale, fit[], item with the colour and size bought, photos[] and brandResponses[]. The first page's stats holds averageRating, ratingCount, reviewCount, ratingDistribution[] and the average fit answers; later pages have stats: null.
id is the 10-digit article id from the product page URL, such as 1240531009. sort takes newest (default), oldest, highest_rating or lowest_rating; limit is 1 to 100 (default 20). Pass page.nextCursor as cursor for the next page.
Price
From $4.05 per 1,000 requests
3 credits per request. Failed requests are free.
- Scale pack
- $4.92 / 1,000
- Growth pack
- $7.08 / 1,000
The lowest rate is on annual plans; packs are pay as you go.
Example request
Send your API key in the x-api-key header. New accounts get 100 free credits, no card needed.
Example response
A 200 response. Live responses have the same shape with current data.
H&M Product Reviews API FAQ
Are reviews of other colours included?
Yes. Reviews of every colour and size are listed together, as on the product page. item says which colour and size each review was left on.
What do the fit averages mean?
Each fit question, such as True to Size or Length, has three answers from lowest to highest, such as Runs Small, True to Size and Runs Large. average runs from 0 to 2 across them, so 1 means reviewers say it is true to size.
What if a product has no reviews?
The answer is lookupStatus found with an empty reviews list. lookupStatus not_found means H&M has no product with that id in the market.
How much does a page of reviews cost?
Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth. Each paginated page is a separate billed request.