/street11/products/search

POST /api/street11/products/search

Price: 20 credits

Search 11Street products by keyword with filters (sort, price range, brand, seller, category, product type, benefit, delivery, attribute): returns product cards with price, rating, seller and review count.

How to use it

Search 11Street (11번가) products by keyword. Each result has id (prdNo), name (Korean), url, image, price/list_price/discount_percent (KRW), rating (0-5), review_count, brand, seller_id/seller_name/seller_url, catalog_no, price_compare_count (same-product offers count), delivery, discount_text (lowest-price badge), recommendation, is_official, is_lowest_price, is_sold_out. Filters: sort (ranking/popular/price_low/price_high/sales/most_reviews/newest), price_min/price_max, brand (brandCd), seller (sellerNos), category (searchCategoryLarge id), product_type, benefit, delivery, attribute (facetCode_valueCode). Returns up to count products. X-Total-Available-Results carries the total match count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "노트북"; minLength: 1)
• count integer required — Max number of products to return (min: 1)
• sort string — Result ordering (default: "ranking"; one of: "ranking", "popular", "price_low", "price_high", "sales", "most_reviews", "newest")
• price_min integer nullable — Minimum price in KRW (min: 0)
• price_max integer nullable — Maximum price in KRW (min: 0)
• brand string nullable — Brand id (brandCd) to filter by
• seller string nullable — Seller number (sellerNos) to filter by
• category string nullable — Display category id (searchCategoryLarge) to filter by
• product_type string nullable — Product type filter (one of: "global_direct", "global_direct_except", "used", "refurbished", "deal", "rental", "displayed", "returned")
• benefit string nullable — Discount/points benefit filter (one of: "hope_shopping", "pay11_point")
• delivery string nullable — Delivery benefit filter (one of: "free_delivery", "safety_install", "free_gift_wrapping")
• attribute string nullable — Category attribute facet, format facetCode_valueCode (examples: "41614_12723")

Response

• @type string (default: "Street11SearchProduct")
• id string required
• name string nullable
• url string nullable
• image string nullable
• price number nullable
• list_price number nullable
• discount_percent number nullable
• rating number nullable
• review_count integer nullable
• brand string nullable
• seller_id string nullable
• seller_name string nullable
• seller_url string nullable
• catalog_no string nullable
• price_compare_count integer nullable
• delivery string nullable
• discount_text string nullable
• recommendation string nullable
• is_official boolean nullable
• is_lowest_price boolean nullable
• is_sold_out boolean 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.