/musinsa/snaps/search

POST /api/musinsa/snaps/search

Price: 10 credits

Search Musinsa (무신사) style snaps by keyword, model gender and format: caption, media, tags, model, likes, comments, views, author and the tagged products with prices

How to use it

Without a keyword the newest or most popular snaps across Musinsa are returned.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Search keyword (examples: "반팔"; minLength: 1)
• gender string — Model gender (default: "all"; one of: "all", "men", "women")
• format_type string — Snap format (default: "all"; one of: "all", "post", "shorts")
• sort string — Result order (default: "popular"; one of: "popular", "newest")
• count integer required — Max number of snaps (min: 1; max: 3000)

Response

• @type string (default: "MusinsaSnap")
• id string required
• url string required
• content_type string nullable
• format_type string nullable
• text string nullable
• thumbnail string nullable
• media array (default: [])
  • @type string (default: "MusinsaSnapMedia")
  • type string nullable
  • url string nullable
  • video_id string nullable
  • duration number nullable
• tags array (default: [])
• labels array (default: [])
• model_gender string nullable
• model_height integer nullable
• model_weight integer nullable
• like_count integer nullable
• comment_count integer nullable
• view_count integer nullable
• scrap_count integer nullable
• click_count integer nullable
• product_click_count integer nullable
• products array (default: [])
  • @type string (default: "MusinsaSnapProduct")
  • id string nullable
  • url string nullable
  • platform string nullable
  • name string nullable
  • image string nullable
  • brand_alias string nullable
  • brand_name string nullable
  • categories array (default: [])
  • currency string (default: "KRW")
  • price number nullable
  • normal_price number nullable
  • discount_rate number nullable
  • coupon_price number nullable
• author object nullable
  • @type string (default: "MusinsaSnapAuthor")
  • id string nullable
  • name string nullable
  • bio string nullable
  • image string nullable
  • type string nullable
  • badge string nullable
• created_at integer nullable
• updated_at integer nullable
• displayed_from integer 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 — 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.