POST /api/daangn/realty/brokers
Price: 1 credit
Get a Daangn (당근) real-estate broker by id: office name and address, listing counts by property type, star-rating counts, chat response time and rate, and its current listings
Broker ids are the broker id of daangn/realty and the brokers of daangn/realty/complexes. Pass a listing id to daangn/realty for the full listing.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)broker string required — Daangn real-estate broker id (examples: "3048118"; minLength: 1)@type string (default: "DaangnRealtyBroker")id string requirednode_id string nullablename string nullablestatus string nullableimage string nullablecity string nullabledistrict string nullableneighborhood string nullableroad_address string nullablejibun_address string nullablelisting_counts object (default: {})* integerbadges array (default: [])rating_counts object (default: {})* integerreview_count integer nullablechat_response_minutes number nullablechat_response_rate number nullableis_direct_chat_available boolean nullableis_business_verified boolean nullablelistings array (default: [])@type string (default: "DaangnBrokerListingRef")id string nullableproperty_type string nullabledistrict string nullableneighborhood string 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 broker 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.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.