/house591/sale_listings

POST /api/house591/sale_listings

Price: 1 credit

Get one property for sale on 591 — a home, a shop, office or factory, or land: asking price, price per ping, area and its breakdown, land section and zoning, building records, facilities, the seller's description, location with nearby places, and the agent's or owner's contact details

How to use it

Find ids with house591/sale_listings/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 — Sale listing id or URL (examples: "20937974", "https://sale.591.com.tw/home/house/detail/2/20937974.html")

Response

• @type string (default: "House591ListingDetail")
• id string required
• url string required
• deal_type string nullable (one of: "rent", "sale")
• status string nullable
• kind_code string nullable
• kind_name string nullable
• building_type string nullable
• price number nullable
• price_unit string nullable
• price_includes_parking boolean nullable
• unit_price number nullable
• unit_price_unit string nullable
• area number nullable
• area_unit string nullable
• deposit string nullable
• region_id string nullable
• region_name string nullable
• district_id string nullable
• district_name string nullable
• address string nullable
• latitude number nullable
• longitude number nullable
• community_id string nullable
• community_name string nullable
• business_district string nullable
• land_section string nullable
• land_zoning string nullable
• land_number string nullable
• tags array (default: [])
• attributes array (default: [])
  • @type string (default: "House591Attribute")
  • key string nullable
  • label string required
  • value string required
• property_records array (default: [])
  • @type string (default: "House591Attribute")
  • key string nullable
  • label string required
  • value string required
• area_breakdown array (default: [])
  • @type string (default: "House591Attribute")
  • key string nullable
  • label string required
  • value string required
• facilities array (default: [])
• highlights array (default: [])
• description string nullable
• nearby array (default: [])
  • @type string (default: "House591Place")
  • category string nullable
  • kind string nullable
  • name string required
  • distance_m number nullable
  • latitude number nullable
  • longitude number nullable
• contact object nullable
  • @type string (default: "House591ListingContact")
  • user_id string nullable
  • name string nullable
  • role string nullable
  • agency string nullable
  • branch string nullable
  • brokerage string nullable
  • certificate string nullable
  • mobile string nullable
  • phone string nullable
  • email string nullable
  • line_url string nullable
  • image string nullable
  • service_fee string nullable
  • shop_id string nullable
  • shop_name string nullable
  • shop_intro string nullable
  • experience string nullable
  • joined string nullable
  • labels array (default: [])
• image string nullable
• view_count integer nullable
• favorite_count integer nullable
• share_count integer nullable
• posted_at integer nullable
• updated_text string nullable

Errors

• 422 — id is not a 591 listing id or URL 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 property for sale 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.