/naver/land/complexes/transactions

POST /api/naver/land/complexes/transactions

Price: 1 credit

Get the government-recorded deals of one area type of a Naver Real Estate (네이버 부동산) complex, newest first: sale price, or deposit and monthly rent, floor and deal date

How to use it

Take area_no from an area type in naver/land/complexes; complex ids come from naver/land/complexes/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)
• complex string required — Complex id or its Naver Real Estate URL (examples: "111515", "https://new.land.naver.com/complexes/111515")
• area_no integer required — Area type number of the complex (examples: 1; min: 1)
• trade_type string nullable — Deal type. Omit for every deal type (one of: "sale", "jeonse", "monthly_rent")
• count integer required — Max number of transactions to return (examples: 50; min: 1; max: 1000)

Response

• @type string (default: "NaverLandTransaction")
• complex_id string required
• area_no string required
• trade_type string nullable
• trade_type_code string nullable
• sale_price number nullable
• deposit number nullable
• monthly_rent number nullable
• price_text string nullable
• floor integer nullable
• trade_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 or area type 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.