/naver/cafe/trades/search

POST /api/naver/cafe/trades/search

Price: 5 credits

Search second-hand trade listings across Naver Cafes and Naver Flea Market by words, sale status, trade method, product condition, safe payment, price and posting time: title, product, price, status, regions, category, image, cafe

How to use it

Rows with source cafe carry a cafeId/articleId id for naver/cafe/posts, which returns the full listing unless the row sits on a member-only board; that case answers 412 and the row does not show it. flea_market rows link to their Naver Flea Market page.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Words to search for (examples: "캠핑", "아이폰"; minLength: 1)
• count integer required — Max number of results (examples: 50; min: 1; max: 4500)
• sort string — Order of the results (default: "relevance"; one of: "relevance", "newest", "price_low", "price_high")
• statuses array — Sale statuses to include (default: ["on_sale","reserved"]; one of: "on_sale", "reserved", "sold_out"; examples: ["on_sale","reserved"])
• delivery_types array — Trade methods to include (default: []; one of: "meet", "delivery"; examples: ["delivery"])
• conditions array — Product conditions to include (default: []; one of: "new", "almost_new", "used", "heavily_used", "damaged"; examples: ["new","almost_new"])
• safe_payment_only boolean — Only listings that accept Naver safe payment (default: false)
• price_min integer nullable — Lowest price, KRW (examples: 20000; min: 0)
• price_max integer nullable — Highest price, KRW (examples: 200000; min: 0)
• created_from integer nullable — Earliest posting time, unix seconds (examples: 1788188400)
• created_to integer nullable — Latest posting time, unix seconds (examples: 1788793199)

Response

• @type string (default: "NaverCafeTrade")
• id string required
• url string required
• source string required
• product_name string nullable
• price integer nullable
• currency string nullable
• sale_status string nullable
• is_safe_payment boolean nullable
• trade_type string nullable
• delivery_types array (default: [])
• regions array (default: [])
  • @type string (default: "NaverCafeTradeRegion")
  • code string nullable
  • name string nullable
• category string nullable
• category_ids array (default: [])
• image string nullable
• image_count integer nullable
• cafe_id string nullable
• article_id string nullable
• cafe_name string nullable
• cafe_alias string nullable
• is_power_cafe boolean nullable
• is_town_cafe boolean nullable
• menu_id string nullable
• flea_market_product_id string nullable
• created_at 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.