/dabang/complexes

POST /api/dabang/complexes

Price: 5 credits

Get a Dabang (다방) apartment or officetel complex by id or URL: address, households, buildings, floors, parking, heating, builder, approval date, unit types with sizes and maintenance fees, photos, area price averages, nearby complexes and schools

How to use it

Complex ids come from dabang/complexes/search and dabang/places/search. A spaces id narrows dabang/complexes/transactions. 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)
• complex string required — Dabang complex id or complex URL (examples: "58291f833bafe273a02644b301ae", "https://www.dabangapp.com/complex/58291f833bafe273a02644b301ae"; minLength: 1)

Response

• @type string (default: "DabangComplex")
• id string required
• url string required
• name string nullable
• complex_type string nullable
• complex_type_name string nullable
• address string nullable
• jibun_address string nullable
• road_address string nullable
• latitude number nullable
• longitude number nullable
• household_count integer nullable
• building_count integer nullable
• parking_spaces integer nullable
• parking_per_household number nullable
• floors_min integer nullable
• floors_max integer nullable
• building_coverage_ratio number nullable
• floor_area_ratio number nullable
• builder string nullable
• management_office_phone string nullable
• heating_type string nullable
• heating_fuel string nullable
• entrance_type string nullable
• use_approval_date integer nullable
• use_approval_kind string nullable
• recent_deal_count integer nullable
• sale_price_per_pyeong_avg number nullable
• listing_count integer nullable
• primary_space_id string nullable
• hash_tags array (default: [])
• photos array (default: [])
  • @type string (default: "DabangComplexPhoto")
  • text string nullable
  • image string nullable
  • latitude number nullable
  • longitude number nullable
• spaces array (default: [])
  • @type string (default: "DabangComplexSpace")
  • id string nullable
  • pyeong_type string nullable
  • size_type string nullable
  • room_count integer nullable
  • bathroom_count integer nullable
  • area_m2 number nullable
  • supply_area_m2 number nullable
  • contract_area_m2 number nullable
  • maintenance_fee number nullable
  • floor_plan string nullable
  • floor_plan_3d_url string nullable
  • extended_floor_plan string nullable
• area_prices array (default: [])
  • @type string (default: "DabangAreaPrice")
  • scope string nullable
  • sale_price_per_pyeong_avg number nullable
  • jeonse_price_per_pyeong_avg number nullable
• near_complexes array (default: [])
  • @type string (default: "DabangNearComplex")
  • id string nullable
  • name string nullable
  • summary string nullable
  • deal_kind string nullable
  • price_per_pyeong_avg number nullable
• schools array (default: [])
  • @type string (default: "DabangSchool")
  • level string nullable
  • name string nullable
  • code string nullable
  • ownership string nullable
  • distance_m integer nullable
  • school_district string nullable
  • avg_students_per_class integer nullable
  • children_per_teacher number nullable
  • university_admissions integer nullable
  • autonomous_high_school_admissions integer nullable
  • special_high_school_admissions integer nullable
• region object nullable
  • @type string (default: "DabangRegion")
  • id string nullable
  • code string nullable
  • name string nullable
  • full_name string 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 complex 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.