Zoopla UK Property Scraper avatar

Zoopla UK Property Scraper

Under maintenance

Pricing

Pay per event

Go to Apify Store
Zoopla UK Property Scraper

Zoopla UK Property Scraper

Under maintenance

Scrape UK property listings from Zoopla (for-sale or to-rent) — price, address, bedrooms, agent phone, floor plan, EPC, photos, full description. Export to JSON or CSV. We handle the blocks so your dataset stays clean.

Pricing

Pay per event

Rating

0.0

(0)

Developer

DevilScrapes

DevilScrapes

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share


🎯 What this scrapes

Give this Actor a UK location and a listing type and it returns structured Zoopla property rows — price, address, bedrooms, bathrooms, floor area, tenure, EPC rating, key features, agent details, photos, and (optionally) the full listing description and floor plan straight from each property's detail page.

  1. Searches Zoopla for the location + listing type you give it, with optional price and minimum-bedroom filters.
  2. Collects up to your configured cap of listing rows from the search results.
  3. Optionally visits each listing's detail page for the fuller field set — full description, floor plan URL, EPC graph, and full agent phone.
  4. Emits one row per property to the default dataset.

Zoopla is the UK's #2 property portal, and its listing pages are the closest thing to a canonical source for a huge share of the UK's for-sale and to-rent inventory. This is the Zoopla twin of our Rightmove scraper, built to the same field depth so the two feel like a matched product line.

🔥 Features

  • 🛡️ We clear the JS-execution gate Zoopla puts in front of raw HTTP requests — a hardened browser layer renders the page like a real visitor instead of bouncing off a challenge screen.
  • 🌐 We rotate proxy sessions through Apify Proxy — a fresh exit IP and session on every block.
  • 🧭 Built-in UK geo-splash guard — every fetched page is checked for genuine UK Zoopla markers (currency symbol, canonical domain) before its data is trusted, so a bad proxy exit never silently returns wrong-country data.
  • 🧱 We back off when the target pushes back. Partial successes surface with a clear status message — we never silently return an empty dataset.
  • 🎯 Per-listing fault isolation — one bad listing is logged and skipped; it never fails the whole run.
  • 🧊 Pydantic v2 input + output validation — every row is a typed, schema-enforced record; nullable fields are always null, never silently dropped.
  • 💰 Pay-Per-Event pricing — you're charged per listing row written to your dataset, not per page fetched.

💡 Use cases

  • Market research — track UK listing supply, pricing, and inventory mix by area over time.
  • Estate agent competitor monitoring — see what other agents have listed in your patch, at what price, and with what features.
  • Investment screening — filter for-sale or to-rent inventory by area, price, and bedroom count for deal sourcing.
  • Proptech / analytics pipelines — feed structured listing data into a warehouse or model without maintaining your own scraper.

⚙️ How to use it

  1. Click Try for free at the top of the page.
  2. Enter a UK searchLocation (city, district, postcode prefix, or region) and pick listingType (for-sale or to-rent).
  3. Optionally set maxPriceGbp, minBedrooms, and whether to enrich each row from the detail page (enrichDetails).
  4. Click Start. Output streams into the run's dataset.
  5. Export from Storage → Dataset as JSON, CSV, or Excel — or fetch via the API.

📥 Input

FieldTypeRequiredDefaultNotes
searchLocationstringyes"London"Free-form UK location — city, district, postcode prefix, or region.
listingTypestringno"for-sale"for-sale or to-rent.
maxPriceGbpintegernonullUpper price filter. GBP total for for-sale; GBP/month for to-rent.
minBedroomsintegernonullMinimum bedrooms (1-10).
maxPropertiesintegerno50Hard cap on dataset rows (1-500).
enrichDetailsbooleannotrueFetch each property's detail page for full description, floor plan, EPC, and full agent phone.
countryCodestringno"GB"Pinned to GB in v1 — the declared expectation the geo-splash guard checks against.
proxyConfigurationobjectno{"useApifyProxy": true}Apify Proxy spec.

Example input

{
"searchLocation": "London",
"listingType": "for-sale",
"maxProperties": 5,
"enrichDetails": true,
"countryCode": "GB",
"proxyConfiguration": {
"useApifyProxy": true
}
}

📤 Output

Every row is one dataset item — one Zoopla listing.

FieldTypeNotes
listing_idstringZoopla's own listing identifier.
zoopla_urlstringCanonical Zoopla listing detail-page URL.
addressstring | nullDisplay address.
postcodestring | nullUK postcode, when exposed separately.
latitudefloat | nullListing latitude, where public.
longitudefloat | nullListing longitude, where public.
price_gbpinteger | nullHeadline price in GBP.
price_qualifierstring | nullPrice qualifier text, e.g. "Offers in Excess of".
price_frequencystring | nullRent period, e.g. "pcm", or "not specified" for sales.
listing_typestringfor-sale or to-rent.
property_typestring | nulle.g. "Flat", "Detached house".
bedroomsinteger | nullBedroom count.
bathroomsinteger | nullBathroom count.
sqftinteger | nullFloor area in square feet, when published.
tenurestring | nulle.g. "Leasehold", "Freehold".
epc_ratingstring | nullEnergy Performance Certificate rating letter.
epc_graph_urlstring | nullEPC graph image URL (detail-page field).
descriptionstring | nullFull listing description (detail-page field).
key_featuresarrayBulleted key-feature strings.
listing_added_datestring | nullISO-8601 timestamp, when exposed.
agent_namestring | nullListing agent or branch name.
agent_phonestring | nullFull agent phone (detail-page field).
agent_urlstring | nullAgent branch page URL.
photo_urlsarrayListing photo URLs.
floor_plan_urlstring | nullFloor plan image URL (detail-page field).
country_codestringConstant "GB" for v1.
scraped_atstringISO-8601 UTC timestamp.

Nullable fields are null, never omitted, when Zoopla doesn't expose them publicly or enrichDetails was false.

Example output

{
"listing_id": "68912345",
"zoopla_url": "https://www.zoopla.co.uk/for-sale/details/68912345/",
"address": "Gainsford Road, Walthamstow, London",
"postcode": "E17 6ZL",
"latitude": 51.587363,
"longitude": -0.027555,
"price_gbp": 300000,
"price_qualifier": "Offers in Excess of",
"price_frequency": "not specified",
"listing_type": "for-sale",
"property_type": "Flat",
"bedrooms": 1,
"bathrooms": 1,
"sqft": 443,
"tenure": "Leasehold",
"epc_rating": "C",
"epc_graph_url": "https://lc.zoocdn.com/.../epc.png",
"description": "Set on the quiet side ...",
"key_features": ["One Bedroom", "Rear Garden"],
"listing_added_date": "2026-07-19T10:24:23Z",
"agent_name": "Foxtons, Walthamstow",
"agent_phone": "020 3910 6244",
"agent_url": "https://www.zoopla.co.uk/find-agents/branch/foxtons-walthamstow-.../",
"photo_urls": ["https://lc.zoocdn.com/..."],
"floor_plan_url": "https://lc.zoocdn.com/.../floorplan.png",
"country_code": "GB",
"scraped_at": "2026-08-13T10:00:00+00:00"
}

💰 Pricing

Pay-Per-Event — you pay only when these events fire:

EventUSDWhat it is
actor-start$0.05One-off warm-up charge per run.
result-row$0.0035Per listing row written to your dataset.

Example: 1 000 results at the rates above ≈ $3.55. No subscription, no minimum, no card to start — Apify gives every new account $5 of free credit.

🚧 Limitations

v0 covers search-by-location and optional detail-page enrichment only — no sold-price history (Zoopla's separate "house prices" vertical), no map/polygon search (location is a free-text string, not lat/lng bounds), and no OCR of the EPC graph image (we surface the URL instead of rendering it).

❓ FAQ

Is this legal?

We only fetch content Zoopla makes publicly available on its search and listing pages. Respect Zoopla's terms of service before using output commercially.

Why is a field null?

Detail-page fields (epc_graph_url, description, agent_phone, floor_plan_url) are null when enrichDetails is false, or when Zoopla doesn't expose that field publicly for a given listing.

Do I need my own proxy?

No — Apify Proxy is wired in by default.

Why did I get fewer rows than maxProperties?

Zoopla's search pagination for a given location/filter combination can return fewer results than the cap, and any listing that fails to parse is skipped rather than failing the run — check the run's status message for a breakdown.

💬 Your feedback

Spotted a bug, hit a weird edge case, or need a new field? Open an issue on the Actor's Issues tab on Apify Console — we ship fixes weekly and we read every report.