POST /api/musinsa/brands/products
Price: 5 credits
List a Musinsa (무신사) brand's products with category, gender, price range, pre-owned and order filters: name, prices and discounts, review count and score, sold-out flag
Pass a returned id to musinsa/products for the full product. An unknown brand returns an empty list.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)category string nullable — Musinsa category code (examples: "001", "001001"; pattern: ^\d{3,12}$)gender string — Gender section (default: "all"; one of: "all", "men", "women")min_price integer nullable — Lowest price in KRW (examples: 10000; min: 0)max_price integer nullable — Highest price in KRW (examples: 100000; min: 0)used boolean — Return pre-owned (USED) listings instead of new products (default: false)sort string — Result order (default: "popular"; one of: "popular", "newest", "price_low", "price_high", "discount", "most_reviewed")count integer required — Max number of results (min: 1; max: 20000)brand string required — Musinsa brand alias or URL (examples: "musinsastandard", "https://www.musinsa.com/brand/nike")@type string (default: "MusinsaProductCard")id string requiredurl string requiredname string nullableimage string nullablegender string nullablebrand_alias string nullablebrand_name string nullablebrand_url string nullablecurrency string (default: "KRW")normal_price number nullableprice number nullablecoupon_price number nullablefinal_price number nullablediscount_rate number nullablecoupon_discount_rate number nullablefinal_discount_rate number nullableextra_discount_amount number nullablereview_count integer nullablereview_score number nullableis_sold_out boolean nullableis_ad boolean nullablehas_option_price boolean nullableis_lowest_price boolean nullableis_optimal_price boolean nullableused_condition_grade string nullable422 — 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 rejected the request parameters 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.