/daangn/posts/search

POST /api/daangn/posts/search

Price: 5 credits

Search Daangn (당근) neighbourhood community posts around a neighbourhood by keyword and topic, or browse them without a keyword: one row per post with title, text, topic, author, photos, comment and reaction counts

How to use it

Take region_id from daangn/regions/search. Pass a returned id to daangn/posts for the comments. topic keeps the rows whose topic field equals it.

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)
• topic string nullable — Post topic exactly as returned in the topic field of a row (examples: "맛집", "생활/편의", "일반", "동네친구"; minLength: 1)
• count integer required — Max number of posts to return (min: 1; max: 300)

Response

• @type string (default: "DaangnPostCard")
• id string required
• url string required
• text string nullable
• topic string nullable
• author_name string nullable
• region_name string nullable
• images array (default: [])
• comment_count integer nullable
• reaction_count integer nullable
• status string nullable
• created_at integer nullable
• updated_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.