/zoopla/properties

POST /api/zoopla/properties

Price: 1 credit

Get full Zoopla property listing details by listing id (or listing URL): display address, price, bedrooms, bathrooms, reception rooms, floor area, property type, tenure, council tax band, EPC rating, full description, features, highlights, tags, photos, floor plans, videos, coordinates, nearest stations and the selling/letting agent branch.

How to use it

Fetch a single Zoopla property by numeric listing id or a listing URL. Returns one item with id, url, display_address, title, section (for-sale/to-rent), property_type, category, tenure, listing_status, description, published_at, furnishing (furnished/unfurnished/part_furnished for rentals), price (numeric), price_label, price_min, price_max, price_qualifier, price_per_sqft_label, currency, is_auction, bedroom_count, bathroom_count, living_room_count, size_sqft, epc_rating, council_tax_band, chain_free, is_shared_ownership, is_retirement_home, postcode, street_name, property_number, uprn (UK Unique Property Reference Number), region, outcode, coordinates (latitude, longitude), features, highlights, tags, images, floor_plans, videos, nearest_stations (name, distance_miles) and agent (id, name, image, phone, url, is_developer).

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: "ZooplaProperty")
• id string required
• url string nullable
• display_address string nullable
• section string nullable
• property_type string nullable
• category string nullable
• tenure string nullable
• furnishing string nullable
• listing_status string nullable
• description string nullable
• published_at string nullable
• price integer nullable
• price_label string nullable
• price_min integer nullable
• price_max integer nullable
• price_qualifier string nullable
• price_per_sqft_label string nullable
• currency string nullable
• is_auction boolean nullable
• bedroom_count integer nullable
• bathroom_count integer nullable
• living_room_count integer nullable
• size_sqft integer nullable
• epc_rating string nullable
• council_tax_band string nullable
• chain_free boolean nullable
• is_shared_ownership boolean nullable
• is_retirement_home boolean nullable
• postcode string nullable
• street_name string nullable
• property_number string nullable
• uprn string nullable
• region string nullable
• outcode string nullable
• coordinates object nullable
  • @type string (default: "ZooplaCoordinates")
  • latitude number nullable
  • longitude number nullable
• features array (default: [])
• highlights array (default: [])
• tags array (default: [])
• images array (default: [])
• floor_plans array (default: [])
• videos array (default: [])
• nearest_stations array (default: [])
  • @type string (default: "ZooplaNearestStation")
  • name string required
  • distance_miles number nullable
• agent object nullable
  • @type string (default: "ZooplaPropertyAgent")
  • id string nullable
  • name string nullable
  • image string nullable
  • phone string nullable
  • url string nullable
  • is_developer boolean 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.