/naver/shopping/products/search

POST /api/naver/shopping/products/search

Price: 10 credits

Search Naver Shopping products by words with price, shipping, delivery-speed, store-type, membership and rating filters: product id, name, prices and discount, delivery fee, store, rating, reviews, purchases, categories, attributes, ad flag

How to use it

Returns up to 70 products per query, ads included and flagged with is_ad; narrow the query or the filters for a different set.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Product search words (examples: "캠핑의자", "아이폰 16"; minLength: 1)
• count integer required — Max number of products (examples: 40; min: 1; max: 70)
• price_min integer nullable — Lowest price, KRW (examples: 20000; min: 0)
• price_max integer nullable — Highest price, KRW (examples: 100000; min: 0)
• free_shipping boolean — Only products with free shipping (default: false)
• fast_delivery boolean — Only products with fast (today or guaranteed) delivery (default: false)
• arrival_guarantee boolean — Only products with a guaranteed arrival date (default: false)
• official_store boolean — Only products from official or certified stores (default: false)
• brand_store boolean — Only products from brand stores (default: false)
• membership_benefit boolean — Only products with Naver membership benefits (default: false)
• top_rated boolean — Only products rated 4.8 or higher (default: false)

Response

• @type string (default: "NaverShoppingProduct")
• id string required
• url string required
• name string nullable
• rank integer nullable
• listing_type string nullable
• is_ad boolean nullable
• image string nullable
• images array (default: [])
• price integer nullable
• discounted_price integer nullable
• discount_rate integer nullable
• coupon_price integer nullable
• currency string nullable
• delivery_fee integer nullable
• fast_delivery_type string nullable
• mall_name string nullable
• mall_id string nullable
• mall_badge string nullable
• store_product_id string nullable
• store_count integer nullable
• rating number nullable
• review_count integer nullable
• purchase_count integer nullable
• wishlist_count integer nullable
• membership_points integer nullable
• category_ids array (default: [])
• attributes array (default: [])
  • @type string (default: "NaverShoppingAttribute")
  • name string nullable
  • value string nullable
• options array (default: [])
  • @type string (default: "NaverShoppingOption")
  • id string nullable
  • name string nullable
  • lowest_price integer nullable
• promotion string nullable
• is_smartstore boolean nullable
• is_brand_store boolean nullable
• is_overseas boolean nullable
• is_hot_deal boolean nullable
• is_membership_benefit 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.