/daangn/users

POST /api/daangn/users

Price: 5 credits

Get a Daangn (당근) user profile by id or URL: nickname, neighbourhood, manner temperature, review count, their listings on sale and the trade reviews they received

How to use it

User ids are the seller.id of daangn/articles and the user ids in daangn/cars.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "DaangnUser")
• id string required
• numeric_id string nullable
• url string required
• nickname string nullable
• image string nullable
• manner_temperature number nullable
• review_count integer nullable
• region object nullable
  • @type string (default: "DaangnRegion")
  • id string nullable
  • name string nullable
  • city string nullable
  • district string nullable
  • neighborhood string nullable
• articles array (default: [])
  • @type string (default: "DaangnArticleRef")
  • id string nullable
  • url string nullable
  • price number nullable
  • status string nullable
  • image string nullable
  • region_name string nullable
  • chat_count integer nullable
  • favorite_count integer nullable
  • created_at integer nullable
  • boosted_at integer nullable
• reviews array (default: [])
  • @type string (default: "DaangnUserReview")
  • text string nullable
  • reviewer_id string nullable
  • reviewer_name string nullable
  • reviewer_image string nullable
  • reviewer_region string nullable
  • reviewer_was_seller boolean nullable
  • article_image string nullable
  • created_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 user 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.