UK Land Registry Price Paid Tracker avatar

UK Land Registry Price Paid Tracker

Pricing

from $0.50 / 1,000 new-build flag includeds

Go to Apify Store
UK Land Registry Price Paid Tracker

UK Land Registry Price Paid Tracker

Extracts and normalizes HM Land Registry Price Paid transaction records by postcode, region, or date range — real sold prices, property type, tenure, and new-build status from the official free UK government dataset. £0.003 per transaction record.

Pricing

from $0.50 / 1,000 new-build flag includeds

Rating

0.0

(0)

Developer

joseph fadero

joseph fadero

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Share

Extracts and normalizes real HM Land Registry Price Paid transaction records by postcode, region, or date range — actual sold prices, property type, tenure, and new-build status, straight from the official free UK government dataset (Open Government Licence). £0.003 per transaction record returned.

This is a pure official-data actor: no browser, no scraping, no anti-bot risk. It queries HM Land Registry's own public linked-data API directly.

Data source

HM Land Registry publishes Price Paid Data as official Linked Open Data at landregistry.data.gov.uk. Two real access routes exist:

  • Linked-data REST/JSON API (used by this actor): http://landregistry.data.gov.uk/data/ppi/transaction-record.json, filterable by propertyAddress.postcode, propertyAddress.district (region/local authority), min-transactionDate/max-transactionDate, propertyType, and newBuild, with built-in pagination. Verified live during build — returns real, current transaction records in under 2 seconds for a filtered query.
  • SPARQL endpoint: http://landregistry.data.gov.uk/landregistry/query. Also real and live-tested — a simple unfiltered query returns results in ~1 second — but a realistic filtered query (postcode + date range) repeatedly timed out (>55s) during build testing, likely due to the endpoint doing a broad scan for REGEX/date-range filters without an index. The REST/JSON endpoint above answered the equivalent query correctly and quickly, so it is the route this actor uses.

Data update cadence: HM Land Registry publishes Price Paid Data monthly, with a real publication lag (typically 1–3 months). There is no value in running this actor more than once a month — new transactions won't appear between monthly publications.

Inputs

FieldDefaultDescription
postcodes["NW6 4JD"]Full or outward UK postcodes. Free-text formatting (lowercase, missing space) is normalized automatically.
region"" (Camden used as a documented fallback example)Local authority / county name, e.g. Camden, Hertfordshire. Used only when postcodes is empty.
dateFrom2026-06-01Start of transaction date range (inclusive).
dateTo2026-06-30End of transaction date range (inclusive).
propertyTypeanydetached, semi-detached, terraced, flat, or any.
newBuildOnlyfalseOnly return new-build-flagged transactions.

The default input queries real transaction data for postcode NW6 4JD (Kilburn High Road, London) in June 2026 — chosen and verified live during build to guarantee at least one real matching record with zero manual configuration, so the actor's automated QA test run succeeds against real data rather than an empty result set.

Output fields (per transaction)

FieldDescription
addressFull formatted address (flat/house number, street, locality, town, county).
postcodePostcode as recorded by HM Land Registry.
pricePrice paid in GBP.
propertyTypedetached, semi-detached, terraced, flat, or other.
tenurefreehold or leasehold.
newBuildtrue if flagged as a new-build sale.
transactionDateDate of the transaction as recorded.
transactionIdHM Land Registry's unique transaction ID.
scrapedAtISO timestamp of when this actor run fetched the record.

Postcode normalization

UK postcode free text is inconsistent (no space, lowercase, partial). This actor applies the standard, deterministic UK postcode formatting rule: uppercase the input, then insert a single space before the final 3 characters (the standard inward-code length) if one isn't already present. No external lookup is needed — nw64jd becomes NW6 4JD before querying.

Pricing (PPE)

EventPriceTrigger
Actor Start$0.05Per run (built-in, one-time)
Transaction Record Returned$0.003Per real matching transaction record returned (built-in, via Actor.pushData())
Postcode/Region Query No Match$0.001A query runs and zero real matching transactions are found in the requested range
New-Build Flag Included$0.0005Charged additionally when a returned record has a confirmed new-build status

Pricing is set low across the board — this is commodity official government open data, not a scraped or hard-to-reach source, and the price reflects that.

No overlap with other actors on this account

This account also runs a separate actor covering UK procurement/tender data (government contracts, not property sales). This actor is a genuinely distinct dataset — HM Land Registry residential property sale prices — with no overlap in source, schema, or use case.

Notes

  • No API key or authentication required — HM Land Registry's linked-data API is fully public.
  • A defensive 25-page (5,000 record) cap is applied per query to keep broad region + wide date-range queries bounded.