/house591/new_projects/search

POST /api/house591/new_projects/search

Price: 5 credits

Search new-build housing projects (presale and newly built) on 591, across Taiwan or in one city or county and its districts. Each row carries the project's price range per ping, unit sizes, layouts, purpose, address, sales-office phone and hours, promotions and tags.

How to use it

Get a project's full specification, developer, photos and sales progress with house591/new_projects.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of projects to return (min: 1; max: 3000)
• region string nullable — City or county; all of Taiwan when omitted (one of: "taipei", "keelung", "new_taipei", "hsinchu_city", "hsinchu_county", "taoyuan", "miaoli", "taichung", "changhua", "nantou", "chiayi_city", "chiayi_county", "yunlin", "tainan", "kaohsiung", "pingtung", "yilan", "taitung", "hualien", "penghu", "kinmen", "lienchiang")
• district_ids array nullable — District ids within the region (examples: ["5"])
• stage string nullable — Presale or newly built (one of: "presale", "newly_built")

Response

• @type string (default: "House591NewProject")
• id string required
• url string required
• name string nullable
• stage string nullable (one of: "presale", "newly_built")
• purpose string nullable
• region_id string nullable
• region_name string nullable
• district_id string nullable
• district_name string nullable
• address string nullable
• business_district string nullable
• community_id string nullable
• price_text string nullable
• area_text string nullable
• layouts_text string nullable
• phone string nullable
• phone_extension string nullable
• service_hours string nullable
• tags array (default: [])
• promotions array (default: [])
• image string nullable
• updated_date integer nullable

Errors

• 422 — Unknown region or stage, a non-numeric district id, or district_ids without a region 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.

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.