Land Registry Price Paid Data API: What It Returns and How to Use It

This post covers what the Price Paid data actually contains, how the API works, and what you can build with it. You can see it working right now in the live Price Paid demo tool — enter any UK postcode to see recent property sales returned directly from Land Registry.

What the data contains

Each transaction record in the Price Paid dataset contains:

Sale price. The full consideration paid, as recorded by HM Land Registry at the point of registration. This is the actual price paid, not asking price or estimated value.

Date of transfer. The date the transaction completed, not the date it was registered. There is typically a lag of two to eight weeks between completion and registration — transactions from the past two months are therefore incomplete and should not be used for trend analysis.

Property address. The full address as recorded by Land Registry, including PAON (usually the house number or name), SAON (flat number within a building), street, locality, town, district, county and postcode.

Property type. Detached (D), semi-detached (S), terraced (T), flat or maisonette (F), or other (O). Land Registry does not separately identify bungalows.

New build flag. Whether the property was newly built at the time of sale (Y) or an established building (N).

Tenure. Freehold (F) or leasehold (L). Leases of seven years or less are not recorded in the dataset.

Transaction category. Category A covers standard residential sales. Category B covers transfers under a power of sale, repossessions, and buy-to-let transfers.

What the data does not contain: sale prices for commercial properties, properties sold for non-value consideration (transfers between family members, gifts, inheritance), or properties in Scotland, Northern Ireland, the Channel Islands or the Isle of Man.

How to access it via API

There are two ways to query Price Paid data programmatically.

The SPARQL endpoint. HM Land Registry publishes Price Paid data as linked data, queryable via a SPARQL endpoint at landregistry.data.gov.uk. SPARQL is a query language for linked data — similar to SQL but designed for graph databases. The endpoint accepts queries that can filter by address, postcode, date range, property type, tenure and price range. No authentication is required. No API key. The endpoint is publicly accessible.

The bulk download. HM Land Registry also publishes the full dataset as a downloadable CSV file, updated monthly. For applications that need the complete dataset — market analysis tools, academic research, data pipelines — the bulk download is often more practical than querying the API. The file is large (multiple gigabytes for the complete dataset from 1995) but contains the same data as the SPARQL endpoint.

What you can build with it

Sold prices on property listings. The standard “sold prices” feature on estate agent websites. Enter an address, return all previous sales for that property and its immediate neighbours. Previously built using Zoopla or Rightmove data. Directly accessible for free from Land Registry.

Comparable evidence tools. Mortgage brokers and surveyors need comparable sales evidence — what similar properties in the same area sold for recently. An integration that queries by postcode and property type, returning the most recent relevant transactions, automates what’s currently done manually.

Valuation tools. Automated valuation models use transaction history as a key input. Price Paid data provides the raw transaction records that AVMs are trained on. Integrating it directly gives you current data without a data vendor in the middle.

Market trend reporting. Aggregating Price Paid data by area, property type and time period produces market trend reports — average prices, volume of transactions, new build premiums.

CRM enrichment for property professionals. When a property is added to a CRM, an integration can automatically pull the transaction history for that address. Context about what the property sold for previously is useful across surveying, mortgage broking and conveyancing use cases.

Limitations to understand before integrating

Registration lag. Transactions from the past two months are incomplete. If you’re building a current market tool, exclude the most recent two months or flag them as provisional.

Address matching. Land Registry addresses are derived from Royal Mail address data, but they’re not always clean. House names are recorded inconsistently, flat numbers appear in different fields, and postcode changes over time mean some historical records use obsolete postcodes. Building robust address matching requires handling these inconsistencies.

Commercial exclusions. Commercial property sales are not in the dataset. If your use case involves mixed-use or commercial properties, Price Paid data will have gaps.

Scotland and Northern Ireland. Not covered. The Price Paid dataset covers England and Wales only.

For the full picture of what Land Registry API integration involves — including the Business Gateway API for professional title register access — see the Land Registry API integration service page. For how to compare the two main Land Registry data products, see Business Gateway API vs Use Land and Property Data. And for pricing on an integration build, see the cost breakdown post.

Related posts

• Business Gateway API vs Use Land and Property Data: which do you need?
• How much does Land Registry API integration cost in 2026?

If you need help building a Land Registry API integration into your property platform or internal tools, I can help. I build custom API integrations for businesses across the UK. See API integration pricing or get in touch.