/dabang/brokers

POST /api/dabang/brokers

Price: 1 credit

Get a Dabang (다방) real-estate broker office by id: office name, representative, address, registration and business numbers, phones, location, listing counts, reviews and member agents

How to use it

Broker ids are agent.id in dabang/rooms. Their listings are in dabang/brokers/rooms.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• broker string required — Dabang broker id (examples: "6a587b1100451c0d715d9644"; minLength: 1)

Response

• @type string (default: "DabangBroker")
• id string required
• name string nullable
• representative string nullable
• address string nullable
• registration_number string nullable
• business_number string nullable
• phone string nullable
• phones array (default: [])
• image string nullable
• greeting string nullable
• latitude number nullable
• longitude number nullable
• is_active boolean nullable
• is_premium boolean nullable
• is_phone_verified boolean nullable
• active_listing_count integer nullable
• completed_listing_count integer nullable
• premium_apartment_count integer nullable
• premium_complex_count integer nullable
• review_count integer nullable
• best_review_count integer nullable
• award_year string nullable
• members array (default: [])
  • @type string (default: "DabangBrokerMember")
  • id string nullable
  • name string nullable
  • role string nullable
  • image string nullable
  • is_active boolean nullable
• registered_date 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 — Dabang 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.

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.