/musinsa/products/similar

POST /api/musinsa/products/similar

Price: 5 credits

Get the products Musinsa (무신사) recommends on a product page, grouped by recommendation block: same-brand picks, similar items, items bought together; with prices, discounts and review counts

How to use it

Each row names its recommendation block in group and group_title.

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")

Response

• @type string (default: "MusinsaSimilarProduct")
• id string required
• url string required
• name string nullable
• image string nullable
• gender string nullable
• brand_alias string nullable
• brand_name string nullable
• brand_url string nullable
• currency string (default: "KRW")
• normal_price number nullable
• price number nullable
• coupon_price number nullable
• final_price number nullable
• discount_rate number nullable
• coupon_discount_rate number nullable
• final_discount_rate number nullable
• extra_discount_amount number nullable
• review_count integer nullable
• review_score number nullable
• is_sold_out boolean nullable
• is_ad boolean nullable
• has_option_price boolean nullable
• is_lowest_price boolean nullable
• is_optimal_price boolean nullable
• used_condition_grade string nullable
• source_product_id string nullable
• group string nullable
• group_title string nullable

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 — Musinsa has no product under that id 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.