H&M API Scraper

What does H&M API Scraper do?

H&M API Scraper extracts product data directly from the backend APIs used by the official H&M Android app, instead of rendering and scraping HTML pages. Give it one or more search terms and it returns the full product-listing-page (PLP) result set for each — product names, prices, availability, color swatches, sizes/stock, images, and URLs — and, optionally, the deeper product-detail-page (PDP) data for every product found (description, material composition, price validity dates, and category tree).

Because this Actor talks to the app's JSON APIs, it's fast and doesn't need a browser. Run it on demand, on a schedule, or wire it into your pipeline via the Apify API or integrations (Make, Zapier, n8n, Google Sheets, and more).

Why use H&M API Scraper?

• Price and stock monitoring — track H&M prices, discounts, and per-size stock levels for competitor or catalog research.
• Catalog enrichment — pull material composition, category trees, and product codes to enrich an internal product database.
• Market research — sample search results across locales (en_us, en_gb, de_de, ...) to compare regional pricing and assortment.

How to use H&M API Scraper

1. Open the Actor's Input tab.
2. Add one or more Search queries (e.g. jeans, summer dress).
3. Optionally set a Locale, cap the number of items per query, and choose whether to fetch full product details (PDP).
4. Click Start and download the results from the Dataset tab once the run finishes.

Input

Field	Type	Description
searchQueries	array of strings	Search terms to run against the PLP (search) API.
locale	string	Locale for search results, e.g. en_us, en_gb, de_de. Controls language/currency.
maxItemsPerQuery	integer	Max products to collect per query. 0 = unlimited (all pages).
fetchProductDetails	boolean	Also fetch PDP data (description, materials, category tree) for each product.
market	string	Market code for the PDP endpoint, format hm-<country>. Only hm-us is confirmed reliable across product codes.
pdpLang	string	Language code for PDP responses, e.g. en, de.
proxyConfiguration	object	Optional proxy configuration.

See the Input tab for the full JSON schema.

Output

Each dataset item is a flat object combining the PLP product and, if enabled, its matching PDP data — no nested plp/pdp wrapper objects:

{
  "searchQuery": "jeans",
  "locale": "en_us",
  "productId": "1353272001",
  "productName": "Slim Jeans",
  "brandName": "H&M",
  "price": 29.99,
  "formattedPrice": "$29.99",
  "stockState": "Available",
  "inStock": true,
  "colors": ["Denim blue"],
  "articleIds": ["1353272001"],
  "sizes": ["S", "M", "L"],
  "imageUrl": "https://image.hm.com/assets/hm/...jpg",
  "productUrl": "https://www2.hm.com/en_us/productpage.1353272001.html",
  "pdpCode": "1353272001",
  "pdpName": "Slim Jeans",
  "description": "...",
  "currency": "USD",
  "priceValidFrom": "2026-02-03T23:00:00+00:00",
  "priceValidTo": "2999-12-31T23:00:00+00:00",
  "mainCategory": "Jeans",
  "supercategories": ["Clothing", "Jeans"],
  "fits": ["Slim fit"],
  "baseProductCode": "1353272_group_001",
  "ancestorProductCode": "1353272"
}

You can download the dataset in various formats such as JSON, HTML, CSV, or Excel from the Dataset tab.

Main output fields

Field	Source	Description
productId	PLP	Product/article code, also used to fetch PDP data.
productName / brandName	PLP	Product display name and brand.
price / formattedPrice	PLP	Listing price, raw and formatted.
stockState / inStock	PLP	Availability.
colors / articleIds	PLP	Color variants and their per-color article ids.
sizes	PLP	Sizes currently in stock.
imageUrl / imageUrls	PLP	Main product image and gallery images.
productUrl	PLP	Link to the product page.
description	PDP	Full product description.
currency / priceValidFrom / priceValidTo	PDP	Price and its validity date range.
mainCategory / supercategories	PDP	Category tree.
baseProductCode / ancestorProductCode	PDP	Links color variants of the same garment together.

Pricing / Cost estimation

This Actor makes lightweight JSON API requests (no browser rendering), so it's cheap to run. Cost scales with the number of search queries, pages per query, and whether PDP detail fetching is enabled (roughly one extra request per product). Apify's free tier is generally enough to try it out on a handful of queries.

Tips

• Leave fetchProductDetails off if you only need listing-level data (price, name, stock) — this roughly halves the number of requests.
• maxItemsPerQuery: 0 collects every page for a query; set a cap for quick sampling runs.
• Only market: "hm-us" is confirmed to reliably resolve product codes on the PDP endpoint; other market codes may return an "Invalid baseStore or locale" error.

FAQ, disclaimers, and support

This Actor calls publicly reachable JSON endpoints used by H&M's own mobile app. It is intended for research and legitimate data-collection use; you're responsible for complying with H&M's Terms of Service and applicable law in your jurisdiction. Endpoint behavior may change without notice. Found a bug or need a custom variant? Open an issue on the Actor's Issues tab.