/daangn/posts

POST /api/daangn/posts

Price: 5 credits

Get a Daangn (당근) neighbourhood community post by id or URL: title, text, topic, hashtags, photos, author with manner temperature, read, reaction and comment counts, and the comments with their replies

How to use it

Post ids come from daangn/posts/search. comment_count is the total; on long threads comments may hold fewer comments than comment_count.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• post string required — Daangn neighbourhood post id or URL (examples: "uxg1bpsmuigo", "https://www.daangn.com/kr/community/역삼-내-회-맛집-uxg1bpsmuigo/"; minLength: 1)

Response

• @type string (default: "DaangnPost")
• id string required
• numeric_id string nullable
• url string required
• text string nullable
• topic string nullable
• topic_id string nullable
• hashtags array (default: [])
• images array (default: [])
• region_id string nullable
• region_name string nullable
• status string nullable
• author object nullable
  • @type string (default: "DaangnWriter")
  • name string nullable
  • image string nullable
  • manner_temperature number nullable
  • region string nullable
  • status string nullable
• comment_count integer nullable
• reaction_count integer nullable
• reactions object (default: {})
  • * integer
• read_count integer nullable
• watch_count integer nullable
• place_name string nullable
• place object nullable
  • @type string (default: "DaangnPlaceTag")
  • id string nullable
  • place_type string nullable
  • name string nullable
  • address string nullable
  • jibun_address string nullable
  • latitude number nullable
  • longitude number nullable
• comments array (default: [])
  • @type string (default: "DaangnComment")
  • id string nullable
  • parent_id string nullable
  • text string nullable
  • image string nullable
  • status string nullable
  • author object nullable
    • @type string (default: "DaangnWriter")
    • name string nullable
    • image string nullable
    • manner_temperature number nullable
    • region string nullable
    • status string nullable
  • reactions object (default: {})
    • * integer
  • place object nullable
    • @type string (default: "DaangnPlaceTag")
    • id string nullable
    • place_type string nullable
    • name string nullable
    • address string nullable
    • jibun_address string nullable
    • latitude number nullable
    • longitude number nullable
  • created_at integer nullable
  • replies array (default: [])
• created_at integer nullable
• updated_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 — Daangn has no post under that id 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.