POST /api/daangn/cafes/post
Price: 20 credits
Get a Daangn (당근) cafe post by URL: title, text, images, board, author, view, like and comment counts, and the comments with their replies
Post URLs come from daangn/cafes/posts. A members-only post returns no text. Returns up to 2,020 top-level comments, each with its replies.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)post string required — Daangn cafe post URL (examples: "https://cafe.daangn.com/samseonglaion-1/posts/김지찬-고향에-걸린-플랜카드-jvOlgQLA"; minLength: 1)@type string (default: "DaangnCafePost")id string requiredalias string requiredurl string requiredcafe_id string nullablecafe_alias string nullablecafe_name string nullableboard_id string nullableboard_name string nullabletitle string nullabletext string nullableimages array (default: [])is_members_only boolean nullablemembers_only_reason string nullableauthor_name string nullableauthor_image string nullableauthor_member_type string nullableauthor_region string nullableauthor_verification_count integer nullableview_count integer nullablelike_count integer nullablecomment_count integer nullablecomments array (default: [])@type string (default: "DaangnCafeComment")id string nullabletext string nullableauthor_name string nullableauthor_image string nullableauthor_role string nullableauthor_grade_level integer nullableis_author_deleted boolean nullableimages array (default: [])gif string nullablelike_count integer nullablehidden_state string nullablereply_count integer nullablereplies array (default: [])created_at integer nullablecreated_at integer nullableupdated_at integer nullable422 — 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 cafe post at that URL 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.