Blog / API guides

Zoopla API: UK Listings and Sold Prices as JSON

10 Jul 2026Perceptlayer7 min read

Zoopla's own API access is for its member agents and approved partners, not for anyone with a key. To read Zoopla listings, sold prices and valuation history as JSON, the Perceptlayer Zoopla API has 17 GET endpoints at 1 credit per successful call. Resolve a place with /v1/zoopla/locations, search it with /v1/zoopla/search, then pull sold records with /v1/zoopla/sold and a single property's history by its UPRN.

Is there an official Zoopla API?

Not one you can sign up for and use to read listings. The APIs Zoopla documents are for its members' products, such as Premium Listings and Featured Properties, and its authentication guide describes OAuth 2.0 client credentials that Zoopla issues and revokes through your technical contact (Zoopla tech documentation, 2023). The site's terms of use say you may not use its content for commercial purposes without a licence from Zoopla, and they name developing an AI system as one such use (2026).

That gives you two routes. If you're building a commercial product on Zoopla's data, such as a valuation tool you sell, ask Zoopla for a licence: it's the only route that gives you the rights to redistribute. If you need structured Zoopla data for analysis, research or an internal tool, the Zoopla API returns it as JSON with one key. Whether your use is allowed still depends on Zoopla's terms and UK law, and Perceptlayer can't advise on that.

What can the Zoopla API return?

Seventeen endpoints cover three jobs: finding listings in an area, reading sold prices and market statistics, and looking up one property by its Unique Property Reference Number (UPRN). Every endpoint is a GET request, returns JSON and costs 1 credit when it succeeds. The table groups them by what you pass in, which is the order you'll call them.

The UPRN endpoints are the part a listings search can't give you. A UPRN identifies the property rather than a listing, so it stays the same across sales and lettings, and it is the key to join Zoopla records to your own address data.

How do you search Zoopla listings?

Call GET /v1/zoopla/search with a location and, optionally, a section and a page. The location can be an outcode such as sw1a; if you start from a place name, call /v1/zoopla/locations with it first and use what it returns. section picks the listing type: for-sale, to-rent or new-homes. This request asks for the first page of homes for sale in SW1A:

curl "https://api.perceptlayer.com/v1/zoopla/search?location=sw1a&section=for-sale&page=1" \
  -H "X-API-Key: $API_KEY"

Keys start with sk_live_ and go in the X-API-Key header; get a free API key and see the authentication docs for the rest.

These are all the search parameters. Nothing else about them is documented, so don't rely on a default sort or page size.

GET /v1/zoopla/search-count takes the same location and section and returns the count for that search, which tells you how many pages to expect before you spend credits on them. We don't have a recorded Zoopla response to show here, so run the call in the playground on the Zoopla API page to see the fields for yourself.

How do you get Zoopla sold prices?

Use GET /v1/zoopla/sold for sold records in an area. It takes a required location and four optional parameters: from_last_sale_date and to_last_sale_date bound the sale dates, and first and after page through the results. The names follow the usual cursor pattern, where first is how many records to return and after is the cursor from the previous page. Check the response in the playground for where the cursor appears.

curl "https://api.perceptlayer.com/v1/zoopla/sold?location=sw1a&first=50" \
  -H "X-API-Key: $API_KEY"

For an aggregate rather than a list, GET /v1/zoopla/sold-summary takes one or more paths[] values, each up to 120 characters, with optional section and location. GET /v1/zoopla/market-activity gives market activity for a geo (up to 32 characters), with range_months from THREE_MONTHS to ALL and house_type of ALL, DETACHED, SEMI_DETACHED, FLAT or TERRACED.

How do you get a property's valuation history by UPRN?

Pass the UPRN to GET /v1/zoopla/property-valuation-history. Every per-property endpoint takes the same single uprn parameter, so once you have it, the property record, its valuation history, nearby sold homes, similar homes, demand and agents are each one more call. If you only have an address, call GET /v1/zoopla/addresses with the postcode to find the property among the addresses listed there.

curl "https://api.perceptlayer.com/v1/zoopla/addresses?postcode=SW1A%202EP" \
  -H "X-API-Key: $API_KEY"

curl "https://api.perceptlayer.com/v1/zoopla/property-valuation-history?uprn=100023337105" \
  -H "X-API-Key: $API_KEY"

property-agents also takes an optional transaction_type of SALE or RENT. Note the space in the postcode is URL-encoded as %20.

A short Python loop runs the same lookups for a list of UPRNs and saves each response as it comes, so a failure halfway through doesn't lose the rest:

import json
import os
import requests

BASE = "https://api.perceptlayer.com/v1/zoopla"
HEADERS = {"X-API-Key": os.environ["API_KEY"]}
UPRNS = ["100023337105"]  # your list

for uprn in UPRNS:
    for endpoint in ("property", "property-valuation-history", "property-nearby-sold"):
        r = requests.get(f"{BASE}/{endpoint}", params={"uprn": uprn}, headers=HEADERS, timeout=60)
        if r.status_code != 200:
            print(uprn, endpoint, r.status_code, r.json()["error"]["code"])
            continue
        with open(f"{uprn}-{endpoint}.json", "w") as f:
            json.dump(r.json(), f)
        print(uprn, endpoint, "credits used:", r.headers["X-Credits-Used"])

We haven't run this script against the live API for this article. Each successful call prints credits used: 1. A failed one prints its error code, such as not_found or invalid_parameters, and costs nothing. The errors docs list every code.

What does a postcode sweep cost?

Every Zoopla endpoint costs 1 credit per successful call, so the cost of a sweep is the number of calls. Take 20 outcodes. For each one, a search-count call, 5 pages of search and 4 pages of sold is 10 calls, so 20 × 10 = 200 credits. Valuing 300 of the properties you found, with property-valuation-history and property-nearby-sold for each, adds 300 × 2 = 600 credits.

That's 800 credits, inside the 1,000 free credits every verified account gets each month. Run it weekly and it's 800 × 4 = 3,200 credits a month, within the Starter pack's 10,000. Failed calls return X-Credits-Used: 0, so retries after an error don't add to it. The credits docs explain the balance, and pricing has what packs cost.

When is HM Land Registry data the better source?

For completed sale prices in England and Wales, start with HM Land Registry. Its Price Paid Data covers residential sales in England and Wales sold for value and lodged for registration, is updated monthly, and is free to use for commercial or non-commercial purposes under the Open Government Licence (HM Land Registry, 2026). It is the register, so it is the authoritative price.

It has gaps a listing site fills. The two most recent months are incomplete because registration lags the sale, and it records the price paid, not the asking price, the agent or how a valuation moved over time. Zoopla's endpoints add live listings, asking prices, agents and valuation history by UPRN. A common split is Land Registry for the sold price and Zoopla for everything around it. For Scotland and Northern Ireland, which the Price Paid Data doesn't cover, listing sites matter more. The Rightmove API covers the other large UK portal if you want a second source for the same areas.

To try it now, run a search for your own outcode in the playground on the Zoopla API page.

zooplauk propertysold pricesreal estateuprn