/naver/land/complexes/articles

POST /api/naver/land/complexes/articles

Price: 1 credit

List the for-sale and rental listings of one Naver Real Estate (네이버 부동산) complex, with area type, deal type, price, rent, area, maintenance fee, direction, room, bathroom, floor, loan, parking and feature filters: price, area, floor, broker and tags per listing

How to use it

Complex ids come from naver/land/complexes/search; area_nos are area_no values from naver/land/complexes. Pass a listing id to naver/land/articles for its full details. 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)
• property_types array nullable — Property types; any may match. Omit for every type (one of: "apartment", "apartment_presale_right", "reconstruction", "officetel", "officetel_presale_right", "villa", "row_house", "multi_household_house", "detached_house", "country_house", "store_house", "one_room", "store", "office", "factory_warehouse", "knowledge_industry_center", "building", "land", "redevelopment")
• trade_types array nullable — Deal types; any may match. Omit for every deal type (one of: "sale", "jeonse", "monthly_rent", "short_term_rent")
• sort string — Order of the listings (default: "relevance"; one of: "relevance", "newest", "price_asc", "price_desc", "area_asc", "area_desc")
• price_min integer nullable — Minimum sale price, or deposit for rentals, KRW (examples: 300000000; min: 0)
• price_max integer nullable — Maximum sale price, or deposit for rentals, KRW (examples: 1500000000; min: 0)
• rent_min integer nullable — Minimum monthly rent, KRW (examples: 500000; min: 0)
• rent_max integer nullable — Maximum monthly rent, KRW (examples: 2000000; min: 0)
• area_min_m2 integer nullable — Minimum supply area, m² (examples: 60; min: 0)
• area_max_m2 integer nullable — Maximum supply area, m² (examples: 135; min: 0)
• maintenance_fee_min integer nullable — Minimum monthly maintenance fee, KRW (examples: 100000; min: 0)
• maintenance_fee_max integer nullable — Maximum monthly maintenance fee, KRW (examples: 300000; min: 0)
• building_age_max_years integer nullable — Only buildings completed within this many years (examples: 10; min: 1; max: 100)
• building_age_min_years integer nullable — Only buildings completed at least this many years ago (min: 1; max: 100)
• directions array nullable — Facing directions; any may match (one of: "east", "south_east", "south", "south_west", "west", "north_west", "north", "north_east")
• rooms string nullable — Number of rooms (one of: "one", "two", "three", "four_plus")
• bathrooms string nullable — Number of bathrooms (one of: "one", "two", "three", "four_plus")
• floor string nullable — Floor position (one of: "first", "low", "middle", "high", "top", "basement", "above_first")
• loan string nullable — Mortgage on the property (one of: "none", "under_30_percent")
• parking string nullable — Parking availability (one of: "available", "one_per_household", "one_and_half_per_household")
• deal_options array nullable — Deal conditions; all must match (one of: "urgent_sale", "sale_with_tenant", "small_rental")
• features array nullable — Unit features; all must match (one of: "extended", "fully_renovated", "bathroom_renovated", "kitchen_replaced", "separate_kitchen", "duplex", "rooftop", "balcony", "fully_furnished")
• group_same_property boolean — Show one listing per property advertised by several brokers (default: false)
• complex string required — Complex id or its Naver Real Estate URL (examples: "111515", "https://new.land.naver.com/complexes/111515")
• area_nos array nullable — Area type numbers of the complex; any may match (examples: [1,2])
• count integer required — Max number of listings to return (examples: 20; min: 1; max: 1000)

Response

• @type string (default: "NaverLandListing")
• id string required
• url string required
• status_code string nullable
• property_type string nullable
• property_type_code string nullable
• listing_type string nullable
• listing_type_code string nullable
• trade_type string nullable
• trade_type_code string nullable
• verification_type_code string nullable
• sale_price number nullable
• deposit number nullable
• monthly_rent number nullable
• price_text string nullable
• price_change_state string nullable
• is_price_modified boolean nullable
• floor string nullable
• floors_total integer nullable
• area_name string nullable
• supply_area_m2 number nullable
• exclusive_area_m2 number nullable
• direction string nullable
• building_name string nullable
• description string nullable
• tags array (default: [])
• image string nullable
• image_count integer nullable
• latitude number nullable
• longitude number nullable
• is_location_shown boolean nullable
• is_complex boolean nullable
• is_virtual_address boolean nullable
• same_address_count integer nullable
• same_address_direct_count integer nullable
• same_address_price_max_text string nullable
• same_address_price_min_text string nullable
• premium_price number nullable
• premium_text string nullable
• same_address_premium_max_text string nullable
• same_address_premium_min_text string nullable
• realtor_id string nullable
• realtor_name string nullable
• provider_id string nullable
• provider_name string nullable
• provider_url string nullable
• provider_mobile_url string nullable
• is_direct_trade boolean nullable
• is_owner_checked boolean nullable
• is_safe_lessor boolean nullable
• is_vr_exposed boolean nullable
• confirmed_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 — 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.