/dabang/new_projects

POST /api/dabang/new_projects

Price: 5 credits

Get a Dabang (다방) new-build sale project (분양) by id: state, supply type, address, builder and developer, households, floors, sale prices per unit type with payment split and acquisition tax, subscription schedule and results, regulation, nearby facilities and schools

How to use it

Project ids come from dabang/new_projects/search and dabang/places/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)
• project string required — Dabang new-build sale project id or URL (examples: "693688b64c93301d518e000dc6af"; minLength: 1)

Response

• @type string (default: "DabangNewProject")
• id string required
• url string required
• name string nullable
• state string nullable
• state_code string nullable
• building_types string nullable
• supply_type string nullable
• address string nullable
• jibun_address string nullable
• road_address string nullable
• latitude number nullable
• longitude number nullable
• homepage_url string nullable
• notice_url string nullable
• contact_phone string nullable
• provider string nullable
• developer string nullable
• building_count integer nullable
• floors_above integer nullable
• floors_below integer nullable
• household_count integer nullable
• sale_household_count integer nullable
• areas_text string nullable
• price_text string nullable
• price_range_text string nullable
• price_per_pyeong number nullable
• region_price_per_pyeong number nullable
• is_price_cap boolean nullable
• is_resalable boolean nullable
• restrictions string nullable
• regulation_area string nullable
• benefits array (default: [])
• announcement_date integer nullable
• move_in_text string nullable
• image string nullable
• images array (default: [])
• schedules array (default: [])
  • @type string (default: "DabangSaleSchedule")
  • kind string nullable
  • kind_code string nullable
  • date_from integer nullable
  • date_to integer nullable
• spaces array (default: [])
  • @type string (default: "DabangSaleSpace")
  • id string nullable
  • name string nullable
  • area_m2 number nullable
  • supply_area_m2 number nullable
  • household_count integer nullable
  • room_count integer nullable
  • bathroom_count integer nullable
  • price_text string nullable
  • price number nullable
  • down_payment_percent integer nullable
  • middle_payment_percent integer nullable
  • balance_payment_percent integer nullable
  • acquisition_tax number nullable
  • floor_plan string nullable
• min_winning_score string nullable
• max_competition_rate string nullable
• subscription_spaces array (default: [])
  • @type string (default: "DabangSubscriptionSpace")
  • name string nullable
  • households string nullable
  • price_text string nullable
  • winning_score string nullable
  • competition_rate string nullable
• nearby_facilities array (default: [])
  • @type string (default: "DabangNearbyFacility")
  • kind string nullable
  • name string nullable
  • distance_m integer 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
• listing_count 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 sale project 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.