UK Sold Property Prices — Land Registry & House Price Index
Pricing
from $2.00 / 1,000 sale founds
UK Sold Property Prices — Land Registry & House Price Index
Sold house prices by postcode, street, town, or district from official HM Land Registry data. Monitor new sales on a schedule, pull a property's full sale history, and get monthly average-price statistics. No key, no scraping, no proxies.
Pricing
from $2.00 / 1,000 sale founds
Rating
0.0
(0)
Developer
Heim AI
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
0
Monthly active users
4 days ago
Last modified
Categories
Share
UK Sold Property Prices — Land Registry Price Paid & House Price Index
Official HM Land Registry open data — no API key, no scraping, no proxies, no proxy surcharges. Sold house prices for England & Wales by postcode, postcode district, street, town, or county, back to 1995. Monitor new sales on a schedule, pull a single property's complete sale history, and get monthly average-price statistics for any UK region.
Runs out of the box: every mode is keyless.
What it does
| Mode | Input | Output |
|---|---|---|
sold-prices | postcode(s), postcode district, town, district, or county + optional date/price/type filters | Individual sale transactions |
new-sales-monitor | an area + sinceDays window | Latest recorded sales, newest first — built for schedules |
property-history | one postcode + house number/name | Every recorded sale of that property since 1995 |
area-stats | UKHPI region slug + month range | Monthly average price, MoM/YoY change, sales volume, HPI |
The workflows this was built for
Deal-flow monitoring (investors, agents, sourcers). Run new-sales-monitor on a monthly schedule for your patch (postcodeDistrict: "BS3"). Land Registry publishes new registrations around the end of each month — every run delivers what actually sold and for how much, before portals surface it. Dedupe by transactionId downstream.
Comparables (surveyors, lenders, conveyancers). sold-prices for a postcode or district with fromDate and propertyTypes gives you real transaction comps — actual registered prices, not asking prices.
Valuation context. property-history shows what a specific house sold for in every prior transaction; area-stats overlays the official House Price Index trend for the region.
Example input
{"mode": "new-sales-monitor","postcodeDistrict": "SW11","sinceDays": 60,"minPrice": 300000,"propertyTypes": ["terraced", "flat"],"maxItems": 500}
Example output item
{"type": "sale","transactionId": "3B5CE842-3211-EE3A-E063-4804A8C0D6F1","price": 268500,"currency": "GBP","date": "2025-07-18","propertyType": "terraced","estateType": "freehold","newBuild": false,"category": "standardPricePaidTransaction","paon": "8","street": "SAXON WAY","town": "BATH","district": "BATH AND NORTH EAST SOMERSET","postcode": "BA2 8TR","address": "8 SAXON WAY, PEASEDOWN ST JOHN, BATH, BA2 8TR","url": "https://landregistry.data.gov.uk/data/ppi/transaction/3B5CE842-3211-EE3A-E063-4804A8C0D6F1/current"}
Pricing
Pay per event: sale-found per transaction record, stats-month per UKHPI month-region record. Failed lookups are never charged. Set maxItems to cap spend.
Data sources, coverage & fair use
- HM Land Registry Price Paid Data — every residential sale registered in England and Wales, updated monthly. Scotland and Northern Ireland are not covered (separate registers).
- UK House Price Index — official monthly statistics, published with a ~2 month lag.
Contains HM Land Registry data © Crown copyright and database right 2026. This data is licensed under the Open Government Licence v3.0.
Know the data's limits: transactions appear when registered, typically 2 weeks to 2 months after completion — the monitor is for market intelligence, not same-day alerts. Price Paid Data excludes court-ordered transfers and some non-market sales; category distinguishes standard sales from additional-price-paid records (buy-to-let portfolios, repossessions). This actor is not affiliated with HM Land Registry.
Found this useful? A review on the actor page helps other people find it — and tells me what to build next. Hit a problem? Open an issue and I'll fix it fast.
Telemetry
Each run records one anonymous telemetry event to the developer's own storage: a salted hash of the caller account ID (never the raw ID), the run origin (e.g. web console vs API), and a timestamp. No inputs, results, or personal data are collected - this only measures adoption (distinct and returning users).