POST /api/dabang/complexes/search
Price: 5 credits
Search Dabang (다방) apartment or officetel complexes in a square area around a point, with building age and household filters: one row per complex with address, location, listing counts by deal type and real-transaction sale and jeonse prices
Take the centre from dabang/places/search. Pass a returned id to dabang/complexes for the full record or to dabang/complexes/transactions for deals. Money is in KRW.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)complex_type string required — Complex type (one of: "apartment", "officetel")latitude number required — Latitude of the search centre (min: 33; max: 39)longitude number required — Longitude of the search centre (min: 124; max: 132)radius_km number — Half-width of the square search area around the centre, km (default: 1; max: 5; >: 0)building_age_min_years integer nullable — Minimum building age, years (min: 0)building_age_max_years integer nullable — Maximum building age, years (min: 0)household_min integer nullable — Minimum households, apartment only (min: 0)count integer required — Max number of complexes to return (min: 1; max: 2000)@type string (default: "DabangComplexCard")id string requiredurl string requiredname string nullablecomplex_type string nullablesummary string nullableaddress string nullableneighborhood string nullableregion_id string nullablelatitude number nullablelongitude number nullabledistance_km number nullableimage string nullableactive_listing_count integer nullablelisting_counts object nullable@type string (default: "DabangListingCounts")total integer nullablemonthly_rent integer nullablejeonse integer nullablesale integer nullablerecent_sale_price_text string nullablerecent_sale_price number nullablerecent_jeonse_price_text string nullablerecent_jeonse_price number 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 — Dabang rejected the filter combination 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.