UK Sold House Prices — Residential Sales, England & Wales avatar

UK Sold House Prices — Residential Sales, England & Wales

Pricing

from $0.50 / 1,000 results

Go to Apify Store
UK Sold House Prices — Residential Sales, England & Wales

UK Sold House Prices — Residential Sales, England & Wales

HM Land Registry's Price Paid data as flat rows — price paid, date, property type, tenure, new-build flag and the full address. The official record of every residential sale. Free and key-less.

Pricing

from $0.50 / 1,000 results

Rating

0.0

(0)

Developer

alaudin burki

alaudin burki

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

21 days ago

Last modified

Features

Limited permissions

Share

UK Sold House Prices — Every Residential Sale, England & Wales

Reads HM Land Registry's Price Paid data — the official record of residential sales in England and Wales — and returns one flat row per transaction: the date, the price actually paid, property type, tenure, new-build flag and the full address. The register publishes this as open linked data; the Actor queries it through the register's public SPARQL endpoint, so no key is needed. Rows come back newest first, identified by the register's own transaction ID.

How to use

  1. Set postcode to the full postcode you want to read, e.g. WA2 8SN. It is required: the register's national scan does not answer inside a run's time budget, so the Actor reads one postcode at a time.
  2. Set maxItems (default 500) and maxPages (default 5). Each request returns up to 100 records.
  3. Run the Actor. Rows land in the default dataset, and SUMMARY reports the row count, the stop reason and whether the result was truncated.

Inputs

FieldWhat it doesDefault
postcodeThe full postcode to read, e.g. WA2 8SN. Case and spacing do not matter. A partial code is refused rather than expanded — the register would have to scan the country for it.required
maxItemsHard row cap. The runner also refuses to go above 20,000.500
maxPagesHard request cap, 100 records per request. The runner also refuses to go above 200.5
{
"postcode": "NR3 3XP",
"maxItems": 200
}

Output

One row per transaction record.

FieldMeaning
transactionDateSale date, normalised to YYYY-MM-DD from the API's display format.
pricePaidGbpPrice paid, in whole pounds sterling, as recorded by HM Land Registry.
propertyTypeProperty type in the register's categories, title-cased from the register's own term — Terraced, Flat, Flat-maisonette.
estateTypeTenure, title-cased from the register's own term — Freehold or Leasehold.
newBuildBoolean: true when the property was new when sold.
recordStatusThe register's own status for the record, taken from the tail of its linked-data node — add, change or similar.
categoryThe record's transactionCategory exactly as the API returns it; a linked-data value, not a plain label.
houseNameThe register's PAON (primary addressable object) — the building name or number, not a "house name" in the everyday sense.
houseNumberThe register's SAON (secondary addressable object) — usually a flat or unit number.
streetStreet from the recorded address.
localityLocality from the recorded address.
townTown from the recorded address.
districtDistrict from the recorded address.
countyCounty from the recorded address.
postcodePostcode of the recorded address, as published.
sourceAlways hm-land-registry.
fullAddressBuilt by this Actor from SAON, PAON, street, locality, town and postcode, joined with commas. District and county are not included.

Every row also carries id (lr: followed by the register's transaction ID) and scrapedAt (an ISO timestamp for the run), added by the runner and not part of the declared schema. Absent values are dropped from the row rather than written as empty strings.

Limitations

  • England and Wales only. Scotland and Northern Ireland each have a separate land register, and neither is included.
  • This is Price Paid data, not the register of title. It carries no title number, no buyer or seller name, no mortgage or charge details and no lease terms.
  • Not every transfer appears. HM Land Registry excludes some transactions from Price Paid, for example transfers that were not at full market value.
  • Prices are historic, not asking prices. Nothing here reflects what a property is worth today.
  • pricePaidGbp is a whole-pound integer, not a decimal and not pence.
  • houseName and houseNumber are PAON and SAON. They are the two parts of the addressable object, not a name and a number of the same thing, so houseNumber often holds a flat number.
  • recordStatus is a change flag. The same property can appear more than once in the register with different statuses, so filter on the status you want before counting sales.
  • Addresses are as recorded at the time of sale and are not updated when streets are renamed or renumbered.
  • The feed is updated monthly in arrears, so a recent sale may not appear yet.
  • The postcode filter is a filter, not a geocoder. It matches one full postcode exactly as the register stores it; it does not expand outward from a partial code. A postcode is required because the unfiltered national query does not answer inside a run's time budget.

Why this is different

This Actor is different because it reads the official HM Land Registry feed directly, so it returns what was actually paid rather than what someone hoped to get, and it needs no key or scraping layer. Each row is a single transaction with a stable id of lr:<transactionId>, ordered newest first, so two runs over the same period agree. Absent values are omitted rather than blanked, and every run records why it stopped, which makes a capped dataset distinguishable from a complete one.

FAQ

Does it cover Scotland or Northern Ireland? No. Only England and Wales.

Can I get the owner's name or the title number? No. Price Paid data does not contain them; this is a record of sales, not of ownership.

Do I need an API key? No. The endpoint is open and the Actor sends no credentials.

Why does the same property appear twice? Properties that sell more than once have one record per sale. Check transactionDate and recordStatus before treating a pair as a duplicate.

How current is the data? HM Land Registry publishes the feed monthly in arrears, so the most recent weeks are usually missing.

Pricing and limits

The price is shown on the Actor's Apify pricing panel; billing is per event under Apify's pay-per-event model. Each run is bounded by maxItems (default 500, hard-capped at 20,000) and maxPages (default 5, hard-capped at 200), with up to 100 records per request. When a limit stops the run before the feed is exhausted, SUMMARY.truncated is true and SUMMARY.stopReason says which limit was hit.