UK House Prices - Land Registry Price Paid

UK House Prices

UK House Prices gets sold house prices by postcode or street from HM Land Registry Price Paid data (England & Wales, 1995 to now), with a median/mean/min/max summary for each search.

Best for: Lenders and brokers, proptech products, affordability checks, property research and local market analysis.

How to get sold house prices by postcode

1. Add searches to Searches: {"postcode": "LS6 1AA"} or {"street": "Brudenell Road", "town": "Leeds"}.
2. Optionally set Sold since and Max sales per search.
3. Click Start and download the sale rows and summary row.

How it works

Uses HM Land Registry's public linked-data API for Price Paid Data (no key). Contains HM Land Registry data © Crown copyright and database right; licensed under the Open Government Licence v3.0, which allows commercial use with this attribution. Covers England and Wales only. Each search returns sale rows followed by one summary row. Invalid postcodes or failed searches return ok: false and are not charged.

Output

type, price, date, address, postcode, propertyType, tenure, newBuild, medianPrice, ok

Pricing (pay-per-event)

• sale-record: $0.0005 per result ($0.5 / 1,000). Platform usage is included; you pay only for results.
• Example: 10,000 sale records cost $5.00.

Example input

{
  "searches": [
    {
      "postcode": "SW1A 2AA"
    },
    {
      "street": "Brudenell Road",
      "town": "Leeds"
    }
  ],
  "soldSince": "2020-01-01"
}

Example output

Values below are illustrative.

{
  "type": "sale",
  "price": 250000,
  "date": "2021-04-12",
  "address": "51, HEADINGLEY LANE, LEEDS",
  "postcode": "LS6 1AA",
  "propertyType": "semi-detached",
  "tenure": "Freehold",
  "newBuild": false,
  "medianPrice": 164894,
  "ok": true
}

Use it via API, schedules and integrations

Run it in Apify Console, or call it from your own code with the Apify API or the Python and JavaScript clients. Save an input as a task and add a schedule to run it regularly, and send results to Slack, email, webhooks, Zapier, Make or n8n with Apify integrations. AI agents can find and run it through the Apify MCP server.

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("sterlingverify/uk-house-prices").call(run_input={"searches": [{"postcode": "LS6 1AA"}]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Use in Clay, Zapier, Make, n8n, Pipedream, Power Automate or Activepieces

All of them connect to Apify through their official Apify integrations, using your own Apify account: an API token from Apify Console > Settings > API & Integrations, or Apify sign-in for Power Automate. Runs bill to your Apify account at this Actor's pay-per-event price.

• Clay: save this Actor's input as an Apify task and copy it as JSON. In your Clay table, add the Run Apify Actor enrichment, choose it and paste the JSON into Input Data, mapping Clay columns into the fields. To pull a finished run into a new table, use the Import data from Apify Actor source.
• Zapier: use the Apify Run Actor action, or the Finished Actor run trigger followed by Fetch dataset items. Synchronous runs in Zapier stop after 30 seconds, so use the trigger for big batches.
• Make: add the Apify Run an Actor module with Run synchronously set to Yes, then Get Dataset Items with the run's dataset ID. For longer runs, use the Watch Actor Runs trigger.
• n8n: install the Apify node (@apify/n8n-nodes-apify, or search "Apify" on n8n Cloud) and use Run an Actor and get dataset.
• Pipedream: add the Apify app's Run Actor action, or Run Task Synchronously on one of this Actor's public example tasks (or your own saved task) to get the dataset items back in one step. For big batches, start from the New Finished Actor Run or New Finished Task Run trigger, then Get Dataset Items.
• Power Automate: add the Apify connector (a premium connector, currently in preview) and sign in with your Apify account. Use Run Actor with Enter custom value set to sterlingverify/uk-house-prices and paste the input as JSON, then Get dataset items with the run's default dataset ID. For big batches, start the flow from the Actor run finished trigger instead.
• Activepieces: add the Apify piece and use Run Actor, or Run Task on one of this Actor's public example tasks (or your own saved task), then Get Dataset Items. For scheduled or big batches, use the Watch Actor Runs or Watch Task Runs trigger.
• Google Drive / Sheets: add Apify's Upload results to GDrive integration to a scheduled task to drop each run's CSV or XLSX into your team's Drive, or chain the Google Sheets Import & Export actor to append rows to a sheet.
• Slack alerts: add Apify's Slack integration to a scheduled task to post each run's results to your team channel, or start a check from Slack with /apify call and your task ID.
• Any HTTP tool or script: send one request and get the results back as JSON. Runs must finish within 5 minutes.

curl -X POST "https://api.apify.com/v2/acts/sterlingverify~uk-house-prices/run-sync-get-dataset-items" \
  -H "Authorization: Bearer YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json

FAQ

Does it cover Scotland and Northern Ireland?

No. HM Land Registry Price Paid data covers England and Wales only.

How recent is the data?

Price Paid data is published about 2 months after completion and excludes some sales, such as non-market transfers.

Disclaimer

Price Paid data is published about 2 months after completion and excludes some sales (e.g. non-market transfers). Addresses are property addresses, not people, but don't combine them with personal data for marketing without a lawful basis under UK GDPR. Not affiliated with HM Land Registry.

Related sterlingVerify tools

Part of the sterlingVerify UK payments, KYB and data toolkit on Apify Store:

• UK Postcode Enricher: bulk UK postcode lookup with geography and ONS codes
• Bank of England Rates: Bank Rate, SONIA and any Bank of England series
• UK Company Check: Companies House, VAT and UK sanctions KYB check in one call