/dabang/complexes/transactions

POST /api/dabang/complexes/transactions

Price: 5 credits

List the real-estate transactions of a Dabang (다방) complex per unit type over a window of up to 36 months: contract date, sale price, or deposit and monthly rent, floor and registration flags

How to use it

Complex ids come from dabang/complexes/search; unit type ids from the spaces of dabang/complexes. Without dates the window is the last 36 months. 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 — Dabang complex id or complex URL (examples: "58291f833bafe273a02644b301ae", "https://www.dabangapp.com/complex/58291f833bafe273a02644b301ae"; minLength: 1)
• space_id string nullable — Unit type id from dabang/complexes spaces; every unit type when omitted
• deal_kind string — Sales, or jeonse and monthly-rent leases (default: "sale"; one of: "sale", "lease")
• date_from integer nullable — Earliest contract month, unix seconds; month-granular (min: 0)
• date_to integer nullable — Latest contract month, unix seconds; month-granular (min: 0)
• count integer required — Max number of transactions to return (min: 1)

Response

• @type string (default: "DabangTransaction")
• complex_id string required
• space_id string nullable
• contract_date integer nullable
• deal_type string nullable
• deal_type_name string nullable
• sale_price number nullable
• deposit number nullable
• monthly_rent number nullable
• floor integer nullable
• is_released boolean nullable
• is_registered boolean nullable
• is_direct boolean nullable
• is_new boolean 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 — Dabang 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.