UK Land Registry Price Paid Scraper

Extract sold house prices from the public HM Land Registry Price Paid Data API.

Use this actor to collect UK property transaction records by postcode, town, street, price, date, property type, tenure, and new-build status. It returns clean dataset rows for valuation comps, market monitoring, lead research, and proptech analytics.

What does UK Land Registry Price Paid Scraper do?

UK Land Registry Price Paid Scraper queries the official public Price Paid Data endpoint and normalizes each transaction into a flat Apify dataset row.

It can help you answer questions such as:

• 🏠 What homes sold near this postcode?
• 📍 What has sold on a specific street?
• 💷 Which transactions fall within a target price band?
• 📅 What sold after a specific date?
• 🧱 Which records are flats, terraced homes, detached homes, or new builds?

Who is it for?

This actor is useful for teams that need repeatable UK sold-price data.

• 🏘️ Property investors comparing purchase opportunities
• 🏢 Estate and letting agencies researching local comparables
• 📊 Proptech analysts building valuation or market datasets
• 🧾 Mortgage, insurance, and risk teams checking historical sale prices
• 🧑‍💻 Developers adding UK property data to internal tools

Why use this actor?

The raw Land Registry Linked Data API uses nested linked-data objects and verbose field names. This actor handles pagination and converts that response into practical fields for spreadsheets, databases, and workflows.

You get:

• Typed dataset rows
• Stable field names
• Price/date/type filters
• Source URLs for traceability
• PPE pricing so small runs stay cheap

Data source

The actor uses the public HM Land Registry Price Paid Data service at landregistry.data.gov.uk.

No login, cookies, or API key are required for the source.

Input options

You can search with any combination of:

• Postcodes
• Towns or cities
• Localities
• Streets
• Minimum and maximum price paid
• Sold date from / to
• Property types
• Tenure / estate types
• New-build flag
• Maximum transaction count

Output data

Each dataset item is one Land Registry transaction.

Field	Description
transactionId	Land Registry transaction identifier
pricePaid	Sale price in GBP
transactionDateIso	Sale date normalized to YYYY-MM-DD
postcode	UK postcode
fullAddress	Combined address string
propertyType	Detached, semi-detached, terraced, flat/maisonette, or other
estateType	Freehold or leasehold
newBuild	Whether the sale was a new build
sourceUrl	API URL used to retrieve the record

Example output

{
  "transactionId": "D6906A1B-D6D4-4053-83FB-C72E883E9D4E",
  "pricePaid": 83000,
  "transactionDateIso": "1996-09-24",
  "postcode": "SW2 4XR",
  "fullAddress": "26, TENHAM AVENUE, LONDON, LAMBETH, GREATER LONDON, SW2 4XR",
  "propertyType": "flat-maisonette",
  "estateType": "Leasehold",
  "newBuild": false
}

How much does it cost to scrape UK Land Registry sold prices?

The actor uses pay-per-event pricing.

• A small start fee is charged once per run.
• A per-transaction fee is charged only for records saved to the dataset.
• Larger plan tiers receive lower per-record prices.

Because the data source is a public HTTP API and no browser is needed, runs are designed to be low-cost.

How to scrape UK sold prices by postcode

1. Open the actor on Apify.
2. Add one or more postcodes, for example SW2 4XR.
3. Set maxItems to the number of transactions you need.
4. Run the actor.
5. Export the dataset as CSV, JSON, Excel, or via API.

How to scrape sold prices by town

1. Leave postcodes empty.
2. Add a town such as LONDON, MANCHESTER, or BRISTOL.
3. Optionally add property type, tenure, price, or date filters.
4. Run the actor and review the normalized transaction rows.

Tips for best results

• Use postcodes or streets for focused comparable-property research.
• Use towns with a sensible maxItems limit for larger market samples.
• Add date and price filters when you only need recent or target-band transactions.
• Export CSV for spreadsheet analysis and JSON for automation.

Integrations

Use the output in:

• Google Sheets property comp trackers
• Airtable or Notion lead lists
• Internal valuation dashboards
• BI tools such as Power BI or Looker Studio
• CRM workflows for homeowner or landlord research

API usage with Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/uk-land-registry-price-paid-scraper').call({
  postcodes: ['SW2 4XR'],
  maxItems: 100
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/uk-land-registry-price-paid-scraper').call(run_input={
    'postcodes': ['SW2 4XR'],
    'maxItems': 100,
})
print(run['defaultDatasetId'])

API usage with cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~uk-land-registry-price-paid-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"postcodes":["SW2 4XR"],"maxItems":100}'

MCP usage

Connect the actor to Claude Desktop or Claude Code through Apify MCP.

MCP tool URL:

https://mcp.apify.com/?tools=automation-lab/uk-land-registry-price-paid-scraper

Claude Code setup:

$claude mcp add apify-uk-land-registry https://mcp.apify.com/?tools=automation-lab/uk-land-registry-price-paid-scraper

Claude Desktop JSON configuration:

{
  "mcpServers": {
    "apify-uk-land-registry": {
      "url": "https://mcp.apify.com/?tools=automation-lab/uk-land-registry-price-paid-scraper"
    }
  }
}

Example prompts:

• "Find Land Registry sold-price comps for SW2 4XR."
• "Extract 200 London flat transactions and summarize price bands."
• "Build a CSV of sales on Tenham Avenue."

Legality

This actor uses public government data from HM Land Registry. You are responsible for using exported data lawfully and complying with applicable privacy, database, and commercial-use rules.

Troubleshooting: no results

Try a broader town search or check the exact spelling and capitalization used by Land Registry. Some postcodes may have no price-paid records.

Troubleshooting: broad searches

Town-level searches can be very large. Set a practical maxItems value and use date, price, and property-type filters to keep exports focused.

Related scrapers

Other automation-lab actors that may complement this workflow:

• https://apify.com/automation-lab/rightmove-scraper
• https://apify.com/automation-lab/zoopla-scraper
• https://apify.com/automation-lab/google-maps-lead-finder

Field reference

transactionUri links back to the Land Registry transaction resource.

sourceUrl records the API page used for retrieval.

scrapedAt records when the actor saved the row.

paon and saon are Land Registry address fields for primary and secondary addressable objects.

Performance

The actor uses HTTP requests and conservative pagination. It does not launch a browser.

Data quality

The actor preserves official source values where possible and adds normalized helper fields such as transactionDateIso and fullAddress.

Changelog

Initial version: public API extraction, pagination, filters, normalized dataset schema, and PPE charge events.

Support

If you need a filter or output field that is not included, open an Apify issue with an example postcode, town, or street and the expected workflow.

FAQ

Can I search the whole UK?

The default actor is designed for focused searches. Use town, postcode, locality, or street filters plus maxItems.

Does this include current listings?

No. It extracts historical sold-price transactions from HM Land Registry Price Paid Data.

Does it need proxies?

No. The source is a public government API and the actor runs without proxy configuration.

Can I export to Excel?

Yes. Apify datasets can be exported as CSV, Excel-compatible formats, JSON, XML, RSS, or accessed via API.