/naver/land/complexes

POST /api/naver/land/complexes

Price: 5 credits

Get a Naver Real Estate (네이버 부동산) complex by id or URL: address, location, households and rental households, buildings, floors, approval date, parking, heating, builder, listing counts by deal type, photos, and per area type its size, rooms, listing price ranges, official price, property tax, maintenance fees and floor plans

How to use it

Complex ids come from naver/land/complexes/search. An area type's area_no feeds naver/land/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 — Complex id or its Naver Real Estate URL (examples: "111515", "https://new.land.naver.com/complexes/111515")

Response

• @type string (default: "NaverLandComplex")
• id string required
• url string required
• name string nullable
• property_type string nullable
• property_type_code string nullable
• region_code string nullable
• address string nullable
• road_address string nullable
• zip_code string nullable
• latitude number nullable
• longitude number nullable
• household_count integer nullable
• rental_household_count integer nullable
• permanent_rental_household_count integer nullable
• national_rental_household_count integer nullable
• private_rental_household_count integer nullable
• public_rental_household_count integer nullable
• long_term_rental_household_count integer nullable
• other_rental_household_count integer nullable
• building_count integer nullable
• highest_floor integer nullable
• lowest_floor integer nullable
• supply_area_min_m2 number nullable
• supply_area_max_m2 number nullable
• area_names array (default: [])
• sale_listing_count integer nullable
• jeonse_listing_count integer nullable
• monthly_rent_listing_count integer nullable
• short_term_rent_listing_count integer nullable
• floor_area_ratio number nullable
• building_coverage_ratio number nullable
• parking_count integer nullable
• parking_per_household number nullable
• constructor string nullable
• heating_method string nullable
• heating_method_code string nullable
• heating_fuel string nullable
• heating_fuel_code string nullable
• management_office_phone string nullable
• rebuilding_stage string nullable
• rebuilding_household_count integer nullable
• rebuilding_floor_area_ratio number nullable
• approval_date integer nullable
• photos array (default: [])
  • @type string (default: "NaverLandImage")
  • url string required
  • type_code string nullable
  • category string nullable
  • caption string nullable
  • order integer nullable
  • registered_at integer nullable
• area_types array (default: [])
  • @type string (default: "NaverLandAreaType")
  • area_no string required
  • name string nullable
  • name_pyeong string nullable
  • type_code string nullable
  • supply_area_m2 number nullable
  • supply_area_pyeong number nullable
  • exclusive_area_m2 number nullable
  • exclusive_area_pyeong number nullable
  • exclusive_rate number nullable
  • household_count integer nullable
  • room_count integer nullable
  • bathroom_count integer nullable
  • entrance_type string nullable
  • sale_listing_count integer nullable
  • jeonse_listing_count integer nullable
  • monthly_rent_listing_count integer nullable
  • short_term_rent_listing_count integer nullable
  • sale_price_min number nullable
  • sale_price_max number nullable
  • sale_price_text string nullable
  • jeonse_price_min number nullable
  • jeonse_price_max number nullable
  • jeonse_price_text string nullable
  • jeonse_rate_min number nullable
  • jeonse_rate_max number nullable
  • monthly_rent_deposit_min number nullable
  • monthly_rent_deposit_max number nullable
  • monthly_rent_min number nullable
  • monthly_rent_max number nullable
  • monthly_rent_text string nullable
  • sale_price_per_pyeong_min number nullable
  • sale_price_per_pyeong_max number nullable
  • jeonse_price_per_pyeong_min number nullable
  • jeonse_price_per_pyeong_max number nullable
  • official_price_min number nullable
  • official_price_max number nullable
  • official_price_date integer nullable
  • property_tax object nullable
    • @type string (default: "NaverLandPropertyTax")
    • total number nullable
    • property_tax number nullable
    • local_education_tax number nullable
    • city_area_tax number nullable
    • comprehensive_real_estate_tax number nullable
    • decision_tax number nullable
    • rural_special_tax number nullable
  • maintenance_fee_avg number nullable
  • maintenance_fee_summer_avg number nullable
  • maintenance_fee_winter_avg number nullable
  • maintenance_fees array (default: [])
    • @type string (default: "NaverLandMaintenanceMonth")
    • month integer required
    • total number nullable
    • common number nullable
    • heating number nullable
    • other number nullable
  • floor_plans array (default: [])
    • @type string (default: "NaverLandImage")
    • url string required
    • type_code string nullable
    • category string nullable
    • caption string nullable
    • order integer nullable
    • registered_at integer nullable
  • resale_restricted_until integer nullable
  • presale_price number nullable
  • presale_price_text 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 — Naver Real Estate 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.