UK Land Registry Sold Prices: House Price Data, Stats + New-Sales Monitor

Use this to look up UK house sold prices by postcode, street, town or county from HM Land Registry, with median prices and new-sales monitoring.

Beta. Verify any figure you act on at the linked official record. Built on the official HM Land Registry open data endpoint, local unit tests with recorded fixtures, and a live check of the endpoint before release. Open an issue on the Issues tab if a field looks wrong and we fix it fast.

What it does

Search sold house prices in England and Wales from HM Land Registry's official Price Paid Data (open linked-data endpoint, no login, no scraping).

• Search by postcode, town, district or county, optionally narrowed to one street.
• Filter by date range (or "years back"), property type, new build, and a price range.
• Stats: one free summary row per place with count, median, average, min, max and a breakdown by property type.
• Monitor mode: turn on "only new sales since last run" and schedule the actor; each run delivers only sales not seen before (remembered in a named key-value store). A run with nothing new delivers and charges nothing.

Things to know

• Town, district and county names are matched exactly as HM Land Registry records them (case-insensitive), e.g. GREATER MANCHESTER, CITY OF WESTMINSTER. A misspelt name returns no rows.
• Results are newest first. Property type, new build and price filters are applied after fetching; for very large areas add a date range so the matching sales are found quickly. If the actor stops scanning early it says so in the run log.
• Large areas with no date filter can take a minute or more because the public endpoint is slow on them.
• Stats are computed from the sales fetched in the run (the most recent matching sales up to your limit), not the whole history.
• Registration lags completion: sales usually appear in the data a few weeks to a couple of months after the sale date.
• The dataset covers England and Wales only (not Scotland or Northern Ireland).

Use cases

• Estate agents, valuers and investors: comparable sold prices around an address.
• Lead generation for movers, removals, mortgage and home-services businesses: fresh completions in a postcode or town.
• Market monitoring: median price trends by area and property type.

Example input

{ "postcodes": ["M1 1AE"], "yearsBack": 3, "maxItems": 50 }

Monitor new sales weekly:

{ "towns": ["LEEDS"], "propertyTypes": ["detached"], "monitorNewSales": true, "maxItems": 200 }

Output fields

Sale rows: transactionId, price, currency, dateOfTransfer, propertyType, newBuild, tenure (freehold/leasehold), transactionCategory, address, postcode, paon, saon, street, locality, town, district, county, sourceUrl, source, scrapedAt. Summary rows (recordType: "summary"): area, basedOn, count, medianPrice, averagePrice, minPrice, maxPrice, earliestSale, latestSale, byPropertyType.

Pricing

Pay per event: $0.002 per sale record returned (about $2 per 1,000). Actor start $0.00005. Summary rows and already-seen sales are free. Set Maximum cost per run to cap spend.

Licence and privacy

Contains HM Land Registry data (c) Crown copyright and database right. Licensed under the Open Government Licence v3.0, which permits reuse including commercially. The dataset contains property addresses and prices only; it has no buyer or seller names. The sourceUrl links the authoritative record.

Output sample

Each result is one dataset item (JSON, CSV, Excel or via API). Shape taken from the actor's dataset schema; field names and meanings below, not live data:

Field	Meaning
recordType
dateOfTransfer
price
address
propertyType
newBuild
tenure
medianPrice
averagePrice
count
sourceUrl

FAQ

How do I try it quickly? Press Start with the prefilled input; it is a small run.

How is it priced? Pay per event; see the Pricing section above or the Pricing tab. A small run costs very little.

Is this a one-off or can it run on a schedule? Both. Use Apify schedules or the API to run it repeatedly.

What if the source is slow or fails? Failed or rate-limited requests (HTTP 429 or 5xx, network errors) are retried up to 4 attempts with growing waits; if a source stays unavailable the run records a warning instead of returning invented results.

Is the data legal to use? The actor reads public data. You are responsible for using the results in line with applicable law and the source's terms.

Alternatives to UK House Sold Prices

Other ways to get similar data, so you can choose what fits:

• HM Land Registry Price Paid Data downloads: official, bulk files
• Rightmove sold prices: consumer property portal
• Zoopla: consumer property portal

This actor's edge is pay-per-result pricing, no login and ready-to-use structured output. Compare on a small test run before you commit.

Changelog

• 0.2 (2026-10-28): listing refresh (title, description, README sections, console prefills). No change to output fields.
• Earlier: initial release.