/naver/land/complexes/search

POST /api/naver/land/complexes/search

Price: 1 credit

Search Naver Real Estate (네이버 부동산) apartment, officetel and reconstruction complexes by name or place: complex id, type, legal district code, address, location, households, buildings, floors, area range, approval date

How to use it

Pass a row's id to naver/land/complexes for the full complex, naver/land/complexes/articles for its listings or naver/land/complexes/transactions for recorded deals; its region_code feeds naver/land/articles/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Complex name or place to search for (examples: "래미안", "헬리오시티"; minLength: 1)
• count integer required — Max number of complexes to return (examples: 50; min: 1; max: 1000)

Response

• @type string (default: "NaverLandComplexRow")
• 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
• latitude number nullable
• longitude number nullable
• 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
• total_area_min_m2 number nullable
• total_area_max_m2 number nullable
• presale_resale_restriction_code string nullable
• is_rebuild_membership_transferable boolean nullable
• has_tour boolean nullable
• tour_url string nullable
• approval_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 — The entity was not found, or a precondition failed 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.