POST /api/daangn/realty/subscriptions
Price: 1 credit
List Korean new-housing subscriptions (청약) on Daangn (당근) realty: one row per announcement with housing type, region, address, supply count, receipt, rank and winner dates, move-in month and top prices
regions takes short names such as 서울 or 경기; prices are in KRW.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)regions array nullable — Province or metropolitan city short names; any may match (examples: ["서울","경기"])house_types array nullable — Housing type names; any may match (examples: ["APT"], ["신혼희망타운"])count integer required — Max number of housing subscriptions to return (min: 1; max: 200)@type string (default: "DaangnHousingSubscription")id string requiredurl string requiredname string nullablehouse_type string nullablerecruitment_type string nullableregion string nullableaddress string nullablesupply_count integer nullablemove_in_month integer nullablereceipt_start_date integer nullablereceipt_end_date integer nullablespecial_receipt_start_date integer nullablespecial_receipt_end_date integer nullablerank1_receipt_date integer nullablerank2_receipt_date integer nullablewinner_announce_date integer nullabletop_prices array (default: [])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 — The entity was not found, or a precondition failed 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.