/house591/communities/transactions

POST /api/house591/communities/transactions

Price: 5 credits

List the government-registered sale prices (實價登錄) of one 591 community, newest first: date, unit and floor, layout, total price, price per ping with and without parking, areas, parking type and price, and the registry's notes on special transactions

How to use it

Find community ids with house591/communities/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Community id or URL (examples: "5855864", "https://market.591.com.tw/5855864")
• stage string required — Completed-home sales or presale contracts (one of: "completed", "presale")
• count integer required — Max number of transactions to return (min: 1; max: 3000)

Response

• @type string (default: "House591Transaction")
• id string required
• community_id string nullable
• community_name string nullable
• stage string required (one of: "completed", "presale")
• transaction_date integer nullable
• built_date integer nullable
• address string nullable
• floor integer nullable
• floor_text string nullable
• total_floors integer nullable
• layout string nullable
• bedrooms integer nullable
• purpose string nullable
• total_price number nullable
• building_price number nullable
• unit_price_per_ping number nullable
• unit_price_per_ping_with_parking number nullable
• total_area_ping number nullable
• building_area_ping number nullable
• parking_area_ping number nullable
• parking_price number nullable
• parking_type string nullable
• parking_count integer nullable
• has_parking boolean nullable
• is_special boolean nullable
• note string nullable
• special_reason string nullable
• previous_transaction_count integer nullable
• tags array (default: [])

Errors

• 422 — id is not a 591 community id or URL, or an unknown stage 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 community 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.