/daangn/businesses

POST /api/daangn/businesses

Price: 5 credits

Get a Daangn (당근) local business by id or URL: name, category, description, notice, phone, address, coordinates, business registration number, weekly opening hours, price list, rating, review and follower counts, photos, its recent posts and recent reviews with owner replies

How to use it

Business ids come from daangn/businesses/search. Money is in KRW.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• business string required — Daangn local business id or URL (examples: "2chzz131obcy", "https://www.daangn.com/kr/local-profile/고운손헤어샵-2chzz131obcy/"; minLength: 1)

Response

• @type string (default: "DaangnBusiness")
• id string required
• numeric_id string nullable
• url string required
• name string nullable
• description string nullable
• notice string nullable
• promotion string nullable
• category string nullable
• category_path array (default: [])
• tags array (default: [])
• status string nullable
• phone string nullable
• safe_phone string nullable
• website string nullable
• business_registration_number string nullable
• is_verified boolean nullable
• road_address string nullable
• jibun_address string nullable
• address_extra string nullable
• latitude number nullable
• longitude number nullable
• region object nullable
  • @type string (default: "DaangnRegion")
  • id string nullable
  • name string nullable
  • city string nullable
  • district string nullable
  • neighborhood string nullable
• image string nullable
• cover_images array (default: [])
• rating number nullable
• review_count integer nullable
• follower_count integer nullable
• takes_reservations boolean nullable
• opening_hours array (default: [])
  • @type string (default: "DaangnBusinessHours")
  • day string required
  • opens_at string nullable
  • closes_at string nullable
  • break_from string nullable
  • break_to string nullable
  • is_closed boolean nullable
  • is_open_24_hours boolean nullable
• opening_hours_note string nullable
• prices array (default: [])
  • @type string (default: "DaangnBusinessPrice")
  • name string nullable
  • price number nullable
  • max_price number nullable
  • price_kind string nullable
  • description string nullable
  • is_representative boolean nullable
• price_images array (default: [])
• posts array (default: [])
  • @type string (default: "DaangnBusinessPost")
  • id string nullable
  • url string nullable
  • text string nullable
  • images array (default: [])
  • bookmark_count integer nullable
  • comment_count integer nullable
  • created_at integer nullable
  • updated_at integer nullable
• reviews array (default: [])
  • @type string (default: "DaangnBusinessReview")
  • text string nullable
  • rating number nullable
  • reviewer_name string nullable
  • reviewer_image string nullable
  • reviewer_region string nullable
  • reviewer_checkin_count integer nullable
  • product_name string nullable
  • images array (default: [])
  • like_count integer nullable
  • owner_reply string nullable
  • owner_reply_at integer nullable
  • created_at integer nullable
• last_active_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 business 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.