/daangn/articles/search

POST /api/daangn/articles/search

Price: 10 credits

Search Daangn (당근) second-hand listings in a neighbourhood and the ones around it, by keyword, category, price range and sale status: one row per listing with title, description, price, status, photo, neighbourhood, trade location and posting time

How to use it

Take region_id from daangn/regions/search. Pass a returned id to daangn/articles for the seller and full details. Money is in KRW.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• region_id integer required — Daangn neighbourhood (dong) id (examples: 6035; min: 1)
• keyword string nullable — Search keyword (examples: "의자"; minLength: 1)
• category integer nullable — Listing category id (one of: 1, 2, 3, 4, 5, 6, 7, 8, 9, 13, 14, 16, 31, 32, 139, 172, 173, 304, 305, 483, 517)
• price_min integer nullable — Minimum price, KRW (min: 0)
• price_max integer nullable — Maximum price, KRW (min: 0)
• only_on_sale boolean — Exclude reserved and sold listings (default: false)
• count integer required — Max number of listings to return (min: 1; max: 300)

Response

• @type string (default: "DaangnArticleCard")
• id string required
• url string required
• description string nullable
• price number nullable
• status string nullable
• image string nullable
• region_name string nullable
• latitude number nullable
• longitude number nullable
• is_instant_buy boolean nullable
• created_at integer nullable
• boosted_at integer nullable

Errors

• 422 — Daangn has no neighbourhood under that region_id 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.