/zoopla/properties/history

POST /api/zoopla/properties/history

Price: 1 credit

Get the price and listing history of a Zoopla property by listing id (or listing URL): first published date and price, every subsequent price change (drop/increase, amount and percentage) and any recorded historic property sales.

How to use it

Fetch the price history of a single Zoopla property by numeric listing id or a listing URL. Returns one item with id, first_published_at, first_published_price_label, view_count_30day, price_changes (date, price_label, change_label, percentage_change_label, is_price_drop, is_price_increase, is_minor_change), historic_sales (date, price, percentage_change, numeric_change) and historic_listings (date, price, price_type, url, bedroom_count, bathroom_count, living_room_count) — past listing campaigns for the property.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• listing string required — Zoopla listing id or a listing URL containing it (examples: "71487577", "https://www.zoopla.co.uk/for-sale/details/71487577/"; minLength: 1)

Response

• @type string (default: "ZooplaPropertyHistory")
• id string required
• first_published_at string nullable
• first_published_price_label string nullable
• view_count_30day integer nullable
• price_changes array (default: [])
  • @type string (default: "ZooplaPriceChange")
  • date string nullable
  • price_label string nullable
  • change_label string nullable
  • percentage_change_label string nullable
  • is_price_drop boolean nullable
  • is_price_increase boolean nullable
  • is_minor_change boolean nullable
• historic_sales array (default: [])
  • @type string (default: "ZooplaHistoricSale")
  • date string nullable
  • price integer nullable
  • percentage_change number nullable
  • numeric_change integer nullable
• historic_listings array (default: [])
  • @type string (default: "ZooplaHistoricListing")
  • date string nullable
  • price integer nullable
  • price_type string nullable
  • url string nullable
  • bedroom_count integer nullable
  • bathroom_count integer nullable
  • living_room_count integer 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 — Listing not found, expired or removed (well-formed but nonexistent/withdrawn listing 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.