Musinsa Product Scraper 🛍️

Scrape ranked and searched fashion products from Musinsa — Korea's #1 online fashion marketplace — as clean, structured JSON. Get product names, brands, prices, discounts, ratings, review counts, and images in one call.

Built for K-fashion trend research, dropshipping product sourcing, and price monitoring.

---

What it does

This actor pulls product data directly from Musinsa's public product-list JSON API (the same one that powers musinsa.com), so results are fast and complete — no fragile HTML scraping in the happy path. Two modes:

• Ranking — the popularity-ranked products for a Musinsa category (e.g. Tops, Outerwear, Shoes). Each item includes its rank.
• Search — every product matching a keyword (e.g. nike, 맨투맨, cardigan).

If the JSON API is ever unavailable, the actor automatically falls back to extracting the product list from the page's embedded __NEXT_DATA__ payload.

---

Input

Field	Type	Description
mode	string	"ranking" or "search".
query	string	Search mode: a keyword. Ranking mode: a Musinsa category code (see below). Defaults to 001 (Tops) in ranking mode.
gender	string	"A" (all), "M" (men), or "F" (women). Default A.
maxItems	integer	Max products to collect. Default 100.

Common category codes (ranking mode)

Code	Category
001	Tops
002	Outerwear
003	Pants
100	Bags
104	Shoes

You can also use full 6-digit leaf codes (e.g. 001001 = short-sleeve tees) taken from the category menu on musinsa.com.

Input example

{
  "mode": "ranking",
  "query": "001",
  "gender": "A",
  "maxItems": 100
}

{
  "mode": "search",
  "query": "nike",
  "gender": "M",
  "maxItems": 200
}

---

Output

Each product is one dataset record. Prices are in KRW (Korean won). rating is normalized to a 0–5 scale. rank and category are only populated in ranking mode.

{
  "source": "musinsa",
  "product_id": "6543427",
  "name": "워셔블 헨리넥 크롭 반팔 쿨 니트 ( 5Color )",
  "brand": "브렌슨",
  "price_krw": 47400,
  "sale_price_krw": 37900,
  "rating": 4.9,
  "review_count": 31,
  "category": "001",
  "rank": 1,
  "url": "https://www.musinsa.com/products/6543427",
  "image_url": "https://image.msscdn.net/images/goods_img/20260526/6543427/6543427_17811581686328_500.jpg",
  "scraped_at": "2026-07-07T09:21:25+09:00"
}

A full 40-item sample from a real run is in samples/sample-output.json.

Field	Meaning
source	Always "musinsa".
product_id	Musinsa goods number.
name	Product name.
brand	Brand display name.
price_krw	Original/list price (KRW).
sale_price_krw	Discounted price if on sale, else null.
rating	Review score, 0–5.
review_count	Number of reviews.
category	Category code (ranking mode only).
rank	Popularity rank (ranking mode only).
url	Product page URL.
image_url	Thumbnail image URL.
scraped_at	ISO-8601 timestamp (KST, UTC+9).

---

Use cases

• K-fashion trend research — track which brands, silhouettes, and price points are climbing the Musinsa popularity rankings week over week.
• Dropshipping / product sourcing — build a catalog of trending Korean fashion products with images, brands, and prices to source or resell.
• Price & discount monitoring — watch price_krw vs sale_price_krw over time to catch drops and benchmark competitor pricing.
• AI agents & datasets — feed structured fashion data into recommendation models, market dashboards, or LLM agents.

---

Rate limiting & legality

• The actor collects only public, non-authenticated data. It never logs in and never touches private endpoints.
• No personal data is collected — no reviewer names, profiles, or IDs. (Individual review text is not scraped by this actor.)
• Requests are rate-limited: one page at a time with a ≥ 500 ms delay between requests, to stay gentle on Musinsa's servers.
• You are responsible for using the data in line with Musinsa's terms of service and applicable law.

⚠️ Proxy recommendation

Musinsa may block datacenter IPs or high request volumes. For reliable runs — especially at higher maxItems — enable Apify Proxy with the RESIDENTIAL group. The actor automatically uses the proxy configuration you provide (via proxyConfiguration in input) and runs direct when none is set. If you see repeated API HTTP 403/429 errors in the log, switch on residential proxy.