/musinsa/products/reviews

POST /api/musinsa/products/reviews

Price: 5 credits

Get reviews of a Musinsa (무신사) product: text, rating, purchased option, photos, likes, date, reviewer height, weight and level, and fit survey answers

How to use it

Take the product id from musinsa/products/search. An unknown product id returns an empty list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Musinsa product id or URL (examples: "6201789", "https://www.musinsa.com/products/6201789")
• sort string — Review order (default: "most_helpful"; one of: "most_helpful", "newest", "rating_high", "rating_low")
• photo_only boolean — Return only reviews with photos (default: false)
• count integer required — Max number of reviews (min: 1; max: 2000)

Response

• @type string (default: "MusinsaReview")
• id string required
• product_id string nullable
• product_name string nullable
• type string nullable
• type_name string nullable
• text string nullable
• rating number nullable
• option string nullable
• images array (default: [])
• like_count integer nullable
• comment_count integer nullable
• created_at integer nullable
• is_first_review boolean nullable
• channel string nullable
• country string nullable
• reviewer object nullable
  • @type string (default: "MusinsaReviewer")
  • id string nullable
  • name string nullable
  • level integer nullable
  • gender string nullable
  • height integer nullable
  • weight integer nullable
  • image string nullable
  • is_staff boolean nullable
• survey array (default: [])
  • @type string (default: "MusinsaSurveyAnswer")
  • attribute string nullable
  • answers array (default: [])

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.