/centaline/estates/units

POST /api/centaline/estates/units

Price: 1 credit

List every flat in a Hong Kong building, floor by floor, with the property reference number (PRN) and internal unit code of each one. The PRN is the key that CentaEstimate valuations are published against, so this is how you go from a building to the per-unit valuations.

How to use it

List the flats of one Centaline (中原地產) Hong Kong building. Pass a building type code (starts with '1-'), e.g. estate='1-TNNLTHSXHI', plus count. Get building type codes from centaline/properties (field type_code) or centaline/estates/search. Each result's id is the property reference number (PRN) — pass it as unit to centaline/valuations for that flat's CentaEstimate valuation.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lang string — Language of the returned names, addresses and descriptions. (default: "hk"; one of: "hk", "sc", "en")
• estate string required — Centaline building type code (starts with '1-'), or the estate page URL of that building. (examples: "1-TNNLTHSXHI")
• count integer required — Max number of results to return (min: 1)

Response

• @type string (default: "CentalineEstateUnit")
• id string required
• unit string nullable
• floor_label string nullable
• unit_code string 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 — No unit roster published for this building. 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.