/dabang/brokers/rooms

POST /api/dabang/brokers/rooms

Price: 5 credits

List the active listings of a Dabang (다방) broker office: title, room type, deal type, deposit, rent or sale price, size, maintenance fee, complex, location and photos

How to use it

Broker ids are agent.id in dabang/rooms. Pass a returned id to dabang/rooms. 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)
• broker string required — Dabang broker id (examples: "6a587b1100451c0d715d9644"; minLength: 1)
• count integer required — Max number of listings to return (min: 1)

Response

• @type string (default: "DabangBrokerRoom")
• id string required
• number string nullable
• url string required
• broker_id string required
• room_type string nullable
• deal_type string nullable
• price_title string nullable
• deposit number nullable
• rent number nullable
• sale_price number nullable
• summary string nullable
• area_m2 number nullable
• maintenance_fee number nullable
• maintenance_charge_type string nullable
• complex_name string nullable
• latitude number nullable
• longitude number nullable
• image string nullable
• images array (default: [])
• hash_tags array (default: [])
• is_quick_move_in boolean nullable
• is_direct boolean nullable
• is_owner_listing boolean nullable
• is_new_construction boolean nullable
• has_vr_tour boolean 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.