POST /api/naver/land/articles/search
Price: 1 credit
Search Naver Real Estate (네이버 부동산) for-sale and rental listings in a district or neighbourhood, with property type, deal type, price, rent, area, maintenance fee, building age, direction, room, bathroom, floor, loan, parking, household and feature filters: price, area, floor, broker, location and tags per listing
Take region_code from a complex in naver/land/complexes/search, or pass a point. Pass a listing id to naver/land/articles for its full details, broker contacts and taxes. Money is in KRW.
access-token string requiredtimeout 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)region_code string nullable — Korean legal district (법정동) code of a district or neighbourhood (examples: "1168010100")latitude number nullable — Latitude of a point inside the neighbourhood (min: 33; max: 39)longitude number nullable — Longitude of a point inside the neighbourhood (min: 124; max: 132)min_households integer nullable — Only complexes with at least this many households (examples: 500)count integer required — Max number of listings to return (examples: 20; min: 1; max: 1000)@type string (default: "NaverLandListing")id string requiredurl string requiredstatus_code string nullableproperty_type string nullableproperty_type_code string nullablelisting_type string nullablelisting_type_code string nullabletrade_type string nullabletrade_type_code string nullableverification_type_code string nullablesale_price number nullabledeposit number nullablemonthly_rent number nullableprice_text string nullableprice_change_state string nullableis_price_modified boolean nullablefloor string nullablefloors_total integer nullablearea_name string nullablesupply_area_m2 number nullableexclusive_area_m2 number nullabledirection string nullablebuilding_name string nullabledescription string nullabletags array (default: [])image string nullableimage_count integer nullablelatitude number nullablelongitude number nullableis_location_shown boolean nullableis_complex boolean nullableis_virtual_address boolean nullablesame_address_count integer nullablesame_address_direct_count integer nullablesame_address_price_max_text string nullablesame_address_price_min_text string nullablepremium_price number nullablepremium_text string nullablesame_address_premium_max_text string nullablesame_address_premium_min_text string nullablerealtor_id string nullablerealtor_name string nullableprovider_id string nullableprovider_name string nullableprovider_url string nullableprovider_mobile_url string nullableis_direct_trade boolean nullableis_owner_checked boolean nullableis_safe_lessor boolean nullableis_vr_exposed boolean nullableconfirmed_date integer nullable422 — 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 region under that code or point 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.