Complete Guide: How to Scrape Zoopla Listings Using Python
Run the Zoopla Scraper Apify Actor from Python and turn zoopla.co.uk searches for homes to buy or rent into structured rows.

This guide shows how to extract UK property listings from zoopla.co.uk with Python: homes for sale and to rent, searched by location, price and bedrooms, returned as one structured row per listing. The tool is the Zoopla Scraper Apify Actor (reventadata/zoopla-scraper), and you drive it from Python with the official Apify API client.
By the end you will know which inputs the Actor accepts, how it applies them, what a row contains, where its limits are and how to run it on a schedule. The prerequisites are small: Python 3.11 or newer, an Apify account and an API token. Every sample row in this guide comes from a run of the Actor's public example task on 15 November 2026: a London search for homes for sale that returned 10 rows.
TL;DR
In this tutorial you will learn to run reventadata/zoopla-scraper from Python with apify-client, pass a search (locations, listingType, minBedrooms, a price range and a sort order) and read back rows with price, address, bedrooms, property type, agent, publication date and map position. You will also learn the 1,000-listing ceiling Zoopla sets per search, how the rent fields differ from the sale fields, and how to repeat a search on a schedule. The Actor is on the Zoopla Scraper Store page. The outcome is a short script that prints one summary per listing.
Prerequisites and setup
- Python 3.11 or newer. The Apify client for Python 3.x requires it.
- An Apify account. The free plan is enough to try the Actor, and you can sign up with an email address or a GitHub login. Apify Console is the web workspace where runs, logs and datasets live.
- An API token. In Console, open Settings > API & Integrations and copy your personal token.
Install the client and export the token (API client docs):
pip install -U "apify-client~=3.0"
export APIFY_API_TOKEN="your_apify_token_here"
Keep the token in an environment variable, not in the script.
Understanding Zoopla Scraper
Zoopla Scraper reads the public Zoopla search pages for the locations you give, so it needs no login. It returns the fields the site shows for each listing in its results: price, bedrooms, address and map position, property type, the agent or developer branch with its public phone number, photo and floor plan counts, the publication date and, when a listing gives them, bathrooms, floor area and price reductions.
Its capabilities:
- For sale and to rent, any location that has a Zoopla search page, with several locations in one run.
- Filters that Zoopla applies. Minimum bedrooms, minimum and maximum price and the sort order go to the site with the search, so only matching listings are read.
- No repeats. A listing found twice, on another page or under another location, is returned once.
- A clear ending. A search that matches nothing ends with a status message; when a location the site does not know, or pages that cannot be read, leave the run with no rows, it ends as failed with the reason.
Limits to know up front: Zoopla serves at most 40 pages of 25 listings for any search, 1,000 in all. The Actor reads the search results, so a listing's full description and energy certificate are not in the rows. A proxy is handled for you.
Step-by-step walkthrough
Step 1: Open the Actor
Open the Zoopla Scraper page on Apify Store and press Try for free. Console opens the Actor with its input form. This guide uses the API instead, so the only thing you need from the page is the name reventadata/zoopla-scraper.
Step 2: Choose the input
The input has these fields:
| Field | Type | Meaning |
|---|---|---|
locations |
array of strings | Required. Zoopla location slugs, for example london. One search per entry. |
listingType |
string | for-sale (default) or to-rent. |
minBedrooms |
integer | Optional, at least 1. |
minPrice, maxPrice |
integer | Optional, pounds, at least 1. Asking price for sale, monthly rent for rent. |
sortBy |
string | recommended (default) or lowestPrice. |
maxItems |
integer | Cap on rows across all locations. Default 100. |
maxPagesPerLocation |
integer | Optional cap on pages per location, 1 to 40, 25 listings each. |
A slug is the part of a zoopla.co.uk search URL after /property/. The Actor lower-cases it and turns spaces into hyphens. A value in listingType or sortBy that is not on the list is refused before the run starts, with a message naming the field. A minPrice above maxPrice ends the run as failed with a message before any page is fetched.
The input of the example task whose rows this guide uses (listingType is left out, so it takes its default, for-sale):
{
"locations": ["london"],
"maxItems": 10
}
Two more shapes worth trying: {"locations": ["manchester", "leeds"], "listingType": "to-rent", "maxPrice": 1500} for rentals across two cities up to 1,500 GBP a month, and {"locations": ["london"], "sortBy": "lowestPrice", "maxItems": 25} for the cheapest end of a market. In both, add maxPagesPerLocation while you check the output.
Step 3: Run the Actor from Python
import os
from apify_client import ApifyClient
# 1. Initialise the client with your token from the environment
client = ApifyClient(os.environ["APIFY_API_TOKEN"])
# 2. Describe the search: homes for sale in London (the default listing type), at most 10 rows
run_input = {
"locations": ["london"],
"maxItems": 10,
}
# 3. Start the Actor and wait for it to finish
run = client.actor("reventadata/zoopla-scraper").call(run_input=run_input)
if run is None or run.status != "SUCCEEDED":
status = run.status if run else "unknown"
raise SystemExit(f"Run did not succeed (status: {status}).")
# 4. Read the rows from the run's default dataset
items = client.dataset(run.default_dataset_id).list_items().items
print(f"Retrieved {len(items)} listings.\n")
# 5. Print two lines per listing, with a price per square foot worked out here
for item in items:
price, sqft = item.get("price"), item.get("sizeSqft")
price_text = f"{price:,} GBP" if price is not None else "no price"
per_sqft = f"{price / sqft:.0f} GBP/sq ft" if price and sqft else "no floor area"
print(f"{item.get('address')} | {item.get('bedrooms')} bed {item.get('propertyType')} | {price_text} | {per_sqft}")
print(f" {item.get('agentName')}, published {item.get('publishedDate')}, tags: {', '.join(item.get('tags') or [])}")
The script checks the run status before it reads anything, so a failed run stops with a clear message instead of an empty loop. run.status and run.default_dataset_id come from the typed run object that call() returns in apify-client 3.x.
Step 4: Examine the output
The first four listings of the 15 November run, produced by the same print loop over the saved rows:
Retrieved 10 listings.
"Type 2_05" at Fielders Crescent, Barking IG11 | 2 bed flat | 385,000 GBP | 442 GBP/sq ft
Bellway - Fielders Quarter, published 2026-11-13, tags: New home, Chain free
Seagull Lane, London E16 | 3 bed flat | 150,625 GBP | 153 GBP/sq ft
Riverside - Aqua Gardens Royal Eden Docks, published 2026-11-13, tags: New home, Shared ownership, Leasehold
Seagull Lane, London E16 | 3 bed flat | 602,500 GBP | no floor area
Riverside - Aqua Gardens Royal Eden Docks, published 2026-11-13, tags: New home, Shared ownership, Leasehold
Store Road, London E16 | 1 bed flat | 91,250 GBP | 140 GBP/sq ft
Hyde New Homes - Stories Wharf, published 2026-11-13, tags: New home, Shared ownership, Leasehold
Three things show up straight away. The first listing is the only one of the ten without a Shared ownership tag. One row has no sizeSqft, and the script says so instead of dividing. And two rows share the address Seagull Lane, London E16 with the same bedroom count.
Step 5: Rentals
Change listingType to to-rent and the price fields change meaning. price becomes the monthly rent, read from the price Zoopla shows (such as £1,900 pcm), priceUnit says pcm or, for shared accommodation, pppm (per person per month), and pricePerWeek carries the weekly figure. availableFrom holds the availability text and availableFromDate an ISO date when that text is a date. priceUnit, pricePerWeek, availableFrom and availableFromDate were empty on all 10 for-sale rows of the run above.
Step 6: Export the data
Datasets export as JSON, CSV, XML, Excel, HTML table, RSS or JSONL from Console, and through the API with the format parameter (dataset docs). The dataset schema defines an overview view with title, address, price, bedrooms, bathrooms, property type, agent, publication date and URL.
Working with the API
The script uses three calls of the Apify client for Python: client.actor("reventadata/zoopla-scraper").call(run_input=...) starts a run and waits for it, the returned run object gives status and default_dataset_id, and client.dataset(...).list_items().items reads the rows. The same token authenticates all of them.
To react to a finished run without waiting in a script, add a webhook. Its payload resource is the response of the Get Actor run API call, which includes defaultDatasetId (webhook docs).
For repeated searches, save the input as an Apify task and attach a schedule, which runs an Actor or task on a cron expression.
For error handling, check run.status as the script does and read the run log with client.log(run.id).get(). The log ends with Skipped N: reason lines, which count listings dropped as duplicates, and a Pushed N row(s). line. A run that saves nothing ends in one of two ways: SUCCEEDED with a status message when the site answered but nothing matched, FAILED when no row was saved because the location is unknown or pages could not be read. Rows saved before a late stop are kept.
Advanced usage patterns
Several locations in one run. Put them all in locations. Each is a separate search, maxItems counts rows across all of them, and a listing found under two locations is stored once, by id.
Getting past the 1,000 ceiling. A search that matches more than 1,000 listings still ends at page 40. Slice it: run the same location several times with different price bands (minPrice together with maxPrice) or different minBedrooms, and merge on id. The Actor removes duplicates only within one run, so merging across runs is yours to do.
Watching a patch. Run a small search on a schedule, keep the id values you have seen and compare. publishedDate carries the day a listing went up, and flag holds Zoopla's badge such as Just added.
Ranking. Work out price per square foot as the script does, or group by agentName or propertyType in pandas or a spreadsheet.
Volume bounds. maxItems stops the run once that many rows are stored, and maxPagesPerLocation limits the pages read per location. Pages are read one after another, so a large run is slow; start with one page.
Understanding your data
Fields follow the dataset schema. price is a number in GBP and priceLabel is the text Zoopla shows. propertyType is Zoopla's own code, for example flat, terraced, detached, semi_detached, maisonette or studio; it is null when the listing does not state one. bedrooms, bathrooms, livingRooms and sizeSqft are null when the listing does not show them, never 0. isNewHome is true when the listing link sits under /new-homes/.
In the 10 rows of the run above every listing is a new home, every one is flagged Just added, and all ten have isPremium true (displayType is premium on eight and premium_plus on two). Nine carry a Shared ownership tag. Five of the ten rows are at Pier Road, London E16. Four pairs of prices at one address differ by exactly a factor of four (91,250 and 365,000; 101,875 and 407,500; 133,750 and 535,000; 150,625 and 602,500). The rows do not say what separates the members of a pair, so read tags, title and summary before treating them as like for like.
One row from the run, the first of the ten (featureTags cut to its first four entries; everything else as returned):
{
"id": "74769323",
"url": "https://www.zoopla.co.uk/new-homes/details/74769323/",
"listingType": "for-sale",
"title": "2 bed flat for sale",
"address": "\"Type 2_05\" at Fielders Crescent, Barking IG11",
"propertyType": "flat",
"bedrooms": 2,
"bathrooms": null,
"livingRooms": null,
"sizeSqft": 872,
"price": 385000,
"priceCurrency": "GBP",
"priceLabel": "£385,000",
"priceUnit": null,
"pricePerWeek": null,
"priceReduction": null,
"publishedDate": "2026-11-13",
"publishedLabel": "13th Nov 2026",
"flag": "Just added",
"underOffer": false,
"availableFrom": null,
"availableFromDate": null,
"isNewHome": true,
"tags": [
"New home",
"Chain free"
],
"featureTags": [
"balcony",
"bath",
"built_in_wardrobes",
"en_suite"
],
"summary": "Brand new & chain free two double bedroom apartment featuring four juliet balconies, spacious open-plan kitchen/living/dining area & en suite to ...",
"agentName": "Bellway - Fielders Quarter",
"agentPhone": "020 3641 2464",
"agentId": 115115,
"agentUrl": "https://www.zoopla.co.uk/new-homes/developers/branch/bellway-fielders-quarter-barking-115115/",
"imageUrl": "https://lid.zoocdn.com/645/430/60f3e9d06658b42ee5dda966bdab181ffe0ffd69.jpg",
"imageCount": 36,
"floorPlanCount": 1,
"videoCount": 0,
"latitude": 51.521664,
"longitude": 0.118391,
"isPremium": true,
"displayType": "premium",
"location": "london",
"searchUrl": "https://www.zoopla.co.uk/for-sale/property/london/",
"scrapedAt": "2026-11-15T19:31:09+00:00"
}
agentName, agentPhone and agentUrl are returned as the listing shows them. searchUrl is the first page of the Zoopla search a row came from, and location is the slug it was found under.
Troubleshooting guide
The run succeeded with zero rows. Zoopla answered, but nothing matched, for example a low maxPrice combined with a high minBedrooms. The status message says so. Loosen the filters.
The run failed with "location not found". The slug is not one Zoopla resolves. Search on zoopla.co.uk and copy the part after /property/ from the URL.
The run failed because pages could not be read. The status message says the pages could not be read. The log shows which page. Run again later with maxPagesPerLocation set to 1 before widening.
Fewer rows than the site reports. Zoopla serves at most 1,000 listings per search, and your maxItems and page cap also bound the run.
Rows with null fields. A listing without a bedroom, bathroom or floor-area figure has null there. Handle null in your code instead of treating it as an error.
Where to look. The run page in Console shows status and log. For help, use the Actor's Store page.
Best practices
Keep the first run small: maxPagesPerLocation: 1 and a maxItems of 10 show the field shapes before you commit to a long search. Prefer filters that Zoopla applies itself (minBedrooms, minPrice, maxPrice, sortBy) over filtering afterwards. Treat null as a value to handle. Store the id with every record so later runs can be compared. Listings change, so the data describes the moment of the run. Honour Zoopla's terms and data-protection rules for any personal data in your use.
Conclusion and next steps
You now have a script that runs reventadata/zoopla-scraper, checks the run status, reads the rows and prints a price per square foot next to each listing. From here, try to-rent with a maxPrice, set sortBy to lowestPrice, or slice a large location by price band.
For current pricing and details, see the Store page.
Try Zoopla Scraper yourself and let me know what you build!
Resources
- Zoopla Scraper on Apify Store
- Apify API client for Python
- Apify datasets
- Apify schedules
- Apify webhooks
About the author: reventadata builds and publishes data extraction Actors on the Apify Store.
About the author
- Hi, I'm the engineer behind ReventaData. I build pay-per-event Apify Actors that turn public marketplace, classifieds, jobs and real-estate sites into clean, reliable datasets. Here on Hashnode, I share practical tutorials on collecting structured web data with Python and Apify, and on putting it to work: price tracking, lead lists and market analysis. Explore our turnkey scrapers: https://apify.com/reventadata
Comments
Join the discussionNo comments yet. Be the first to comment.




