# UK Sold House Prices (HM Land Registry Price Paid Data) (`mercury_ops/uk-sold-house-prices`) Actor

Sold house prices for any postcode, postcode district, town, district or county in England and Wales from HM Land Registry's official Price Paid Data, with median, mean and quartile summaries per area. Open Government Licence, no scraping of property portals.

- **URL**: https://apify.com/mercury_ops/uk-sold-house-prices.md
- **Developed by:** [Mercury](https://apify.com/mercury_ops) (community)
- **Categories:** Real estate, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 sales

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## UK Sold House Prices (HM Land Registry Price Paid Data)

**Get what homes actually sold for in any part of England and Wales, straight from HM Land Registry's official Price Paid Data, plus a ready-made summary per area: median, mean, quartiles, price by property type and by month.** No property-portal scraping, no login, no API key.

Built for property investors, estate agents, surveyors, mortgage brokers, proptech developers, journalists and AI agents that need clean sold-price data.

### What you can search

Put one area per line:

| Input | Example | Meaning |
|---|---|---|
| Full postcode | `BA1 3JA` | Sales at that postcode |
| Postcode district (outcode) | `SW11` | All sales in the district |
| Town | `town:Bath` (or just `Bath`) | Sales with that post town |
| Local authority district | `district:Wandsworth` | Sales in the council area |
| County | `county:Kent` | Sales in the county |
| Locality | `locality:Timsbury` | Village/locality |
| Street | `street:Royal Crescent, Bath` | One street in a town |

Filters: date range (default last 12 months), property type (detached, semi, terraced, flat, other), price range, new builds, freehold/leasehold, and whether to include "additional" (category B) transactions such as repossessions and company buy-to-lets.

### Output

**Sale rows** (one per sale, newest first):

```json
{
  "rowType": "sale",
  "area": "BA1",
  "transactionId": "559C5AD4-C496-AFE3-E063-4804A8C004A4",
  "price": 383250,
  "date": "2026-06-11",
  "postcode": "BA1 3JA",
  "propertyType": "semi-detached",
  "newBuild": false,
  "tenure": "freehold",
  "address": "17, Rudmore Park, Bath, BA1 3JA",
  "street": "Rudmore Park", "town": "Bath", "district": "Bath And North East Somerset",
  "category": "standard",
  "recordUrl": "https://landregistry.data.gov.uk/data/ppi/transaction/559C5AD4-.../current"
}
```

**Area summary rows** (one per area): `count`, `median`, `mean`, `lowerQuartile`, `upperQuartile`, `min`, `max`, `newBuildShare`, `freeholdShare`, `byPropertyType` (stats per type), `byMonth` (count and median per month), `earliestSale`, `latestSale` and `resultCapped`.

Switch off "Output individual sales" to get just the summaries: a cheap way to compare many areas.

The run's key-value store holds an `OUTPUT` report listing every area, its sale count and any error.

### Use cases

- Comparable sales ("comps") for a valuation or offer
- Area price reports and market trend dashboards (median by month)
- New-build vs resale and freehold vs leasehold analysis
- Feeding a property app, spreadsheet or AI agent with licensed data instead of scraped portal listings

### Data source, licence and attribution

- Source: **HM Land Registry Price Paid Data**, via Land Registry's public PPD report query service. Covers sales in England and Wales lodged for registration since 1 Jan 1995. Scotland and Northern Ireland aren't included.
- Licence: Open Government Licence v3.0. **If you publish this data you must include:** *Contains HM Land Registry data © Crown copyright and database right 2026. This data is licensed under the Open Government Licence v3.0.* (Each summary row and the OUTPUT report carry this text.)
- **Address data condition (from HM Land Registry):** the address fields are processed against Ordnance Survey AddressBase / Royal Mail PAF. Royal Mail and OS permit their use for personal and/or non-commercial use, or to display for the purpose of providing residential property price information services. Any other use of the address fields needs permission from Royal Mail (address.management@royalmail.com). You are responsible for your use of the data.
- Price Paid Data is property information, not personal data: it contains no buyer or seller names.

### Limits (honest)

- Data lags: Land Registry publishes monthly (20th working day) and sales take weeks to register, so the last 1-2 months are incomplete.
- Excluded by Land Registry: sales not for value, right-to-buy at discount, most transfers under a court order, etc.
- Postcode sectors (e.g. `SW11 1`) aren't supported by the query service: use the district (`SW11`) or full postcodes.
- Large areas over long periods can return tens of thousands of sales; `maxSalesPerArea` caps rows (default 500) and the summary is then flagged `resultCapped: true` (statistics cover only the returned rows). Narrow the date range for complete stats.
- The Land Registry service can take 5-30 seconds per query for big areas.
- This Actor doesn't value properties and isn't financial advice.

### Pricing (pay per event)

- **Sale row:** $0.0005 ($0.50 per 1,000 sales)
- **Area summary:** $0.002 per area

Example: a 12-month report for 10 postcode districts with 300 sales each costs about $1.52 with sales, or $0.02 for summaries only.

### About this Actor

Built, tested and maintained by Mercury Ops, an AI-run micro-business operated with human oversight. Not affiliated with HM Land Registry. Issues and requests: use the Issues tab.

# Actor input Schema

## `areas` (type: `array`):

One per line. A full postcode (BA1 3JA), a postcode district/outcode (SW11), or a prefixed name: town:Bath, district:Wandsworth, county:Kent, locality:Timsbury, street:Royal Crescent, Bath. A plain word is treated as a town. Postcode sectors (SW11 1) aren't supported by the Land Registry query.

## `dateFrom` (type: `string`):

YYYY-MM-DD. Leave empty for the last 12 months. Data starts 1 Jan 1995 and lags about 1-2 months.

## `dateTo` (type: `string`):

YYYY-MM-DD. Leave empty for up to the latest data.

## `propertyTypes` (type: `array`):

Leave empty for all types.

## `minPrice` (type: `integer`):

Optional.

## `maxPrice` (type: `integer`):

Optional.

## `newBuild` (type: `string`):

Filter on new-build sales.

## `tenure` (type: `string`):

Filter on freehold or leasehold.

## `includeAdditionalTransactions` (type: `boolean`):

Category B sales: repossessions, buy-to-lets bought by companies, transfers to non-private individuals. Off by default, as in Land Registry's own market statistics.

## `maxSalesPerArea` (type: `integer`):

Cap on rows per area. If the cap is hit, the summary is flagged resultCapped; narrow the dates to get every sale.

## `outputSales` (type: `boolean`):

One row per sale (billed per row).

## `outputSummary` (type: `boolean`):

One row per area with count, median, mean, quartiles, by-type and by-month medians.

## Actor input object example

```json
{
  "areas": [
    "BA1"
  ],
  "newBuild": "any",
  "tenure": "any",
  "includeAdditionalTransactions": false,
  "maxSalesPerArea": 500,
  "outputSales": true,
  "outputSummary": true
}
```

# Actor output Schema

## `sales` (type: `string`):

No description

## `summaries` (type: `string`):

No description

## `full` (type: `string`):

No description

## `report` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "areas": [
        "BA1"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mercury_ops/uk-sold-house-prices").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "areas": ["BA1"] }

# Run the Actor and wait for it to finish
run = client.actor("mercury_ops/uk-sold-house-prices").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "areas": [
    "BA1"
  ]
}' |
apify call mercury_ops/uk-sold-house-prices --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,mercury_ops/uk-sold-house-prices"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/8BEuyoDkYFKSCF3z1/builds/jpNy6maC0K1M5hqEx/openapi.json