/daangn/groups

POST /api/daangn/groups

Price: 1 credit

Get a Daangn (당근) neighbourhood group by id or URL: name, description, category, neighbourhood, member, post and meetup counts, boards, a sample of members with their roles, meetups and recent posts

How to use it

Group ids come from daangn/groups/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• group string required — Daangn group id or URL (examples: "v99whu92ojnm", "https://www.daangn.com/kr/group/v99whu92ojnm/"; minLength: 1)

Response

• @type string (default: "DaangnGroup")
• id string required
• numeric_id string nullable
• url string required
• name string nullable
• description string nullable
• category string nullable
• group_type string nullable
• age_range string nullable
• image string nullable
• cover_image string nullable
• photos array (default: [])
• region object nullable
  • @type string (default: "DaangnRegion")
  • id string nullable
  • name string nullable
  • city string nullable
  • district string nullable
  • neighborhood string nullable
• member_count integer nullable
• post_count integer nullable
• meetup_count integer nullable
• boards array (default: [])
• members array (default: [])
  • @type string (default: "DaangnGroupMember")
  • nickname string nullable
  • image string nullable
  • role string nullable
  • intro string nullable
  • region object nullable
    • @type string (default: "DaangnRegion")
    • id string nullable
    • name string nullable
    • city string nullable
    • district string nullable
    • neighborhood string nullable
• meetups array (default: [])
  • @type string (default: "DaangnGroupMeetup")
  • id string nullable
  • name string nullable
  • status string nullable
  • starts_at integer nullable
  • participants integer nullable
  • max_participants integer nullable
  • place_name string nullable
  • place_city string nullable
  • place_district string nullable
  • latitude number nullable
  • longitude number nullable
  • is_members_only boolean nullable
• recent_posts array (default: [])
  • @type string (default: "DaangnGroupPost")
  • id string nullable
  • url string nullable
  • board string nullable
  • text string nullable
  • author_name string nullable
  • image string nullable
  • comment_count integer nullable
  • reaction_count integer nullable
  • is_members_only boolean nullable
  • created_at integer nullable
• last_active_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 group 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.