# UK Land Registry Price Paid Data (`seaf999ield/uk-land-registry-price-paid`) Actor

Sold house prices for England & Wales from official HM Land Registry Price Paid Data. Search by postcode, district, town, county, date range and property type, and get area comps (median, count, % change vs previous period).

- **URL**: https://apify.com/seaf999ield/uk-land-registry-price-paid.md
- **Developed by:** [RustonRoad](https://apify.com/seaf999ield) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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 Land Registry Price Paid Data: Sold House Prices & Area Comps

**Get sold house prices for England & Wales from the official HM Land Registry Price Paid Data.** Search by **postcode, postcode district, town, local authority district, county, date range, property type, tenure and new build**, and get **area comps**: sales count, **median**, mean, quartiles and **% change vs the previous period**. Official open data, no scraping, no login, no API key.

| Output | What you get |
|---|---|
| 🏠 **Sales** | Every matching sale: price, date, full address, postcode, property type, new build, tenure, PPD category |
| 📊 **Area comps** | Per area (and per property type): sales count, median, mean, p25/p75, min/max, previous period median and count, % change |

### What it does

- Reads the official HM Land Registry **Price Paid Data** yearly files (every residential sale in England & Wales since 1995, updated monthly)
- Filters by **postcode area / district / sector / full postcode**, **town**, **local authority district**, **county** and **street**
- Filters by **date range**, **property type** (detached, semi, terraced, flat, other), **new build**, **tenure** and **price range**
- Builds **comparables** for each area you enter, split by property type, with the change against the same length period before
- Export to CSV, Excel or JSON, or call it from the API, Make, Zapier or n8n

### Who uses it

- **Estate agents and valuers:** sold comps for a postcode or street in seconds.
- **Property investors and sourcers:** median prices and price trends by postcode district.
- **Proptech and data teams:** a clean feed of sold prices for dashboards and models.
- **Journalists and researchers:** local house price stories with official numbers.

### Input

| Field | Example | Notes |
|---|---|---|
| Postcodes | `["SW11", "BS6 5", "M1 1AA"]` | Area, district, sector or full postcode. Each value is its own comps area |
| Towns | `["BRISTOL"]` | Post town |
| Districts | `["WANDSWORTH"]` | Local authority district |
| Counties | `["KENT"]` | |
| Date from / to | `2026-06-01` / `2026-08-31` | Empty = the last 12 months of published data |
| Property types | `["F", "T"]` | D, S, T, F, O |
| New build / Tenure | `any` | |
| Min / max price | `200000` / `600000` | |
| Include category B | `false` | Repossessions, buy to let, non private buyers |
| Output | `salesAndComps` | or `sales`, `comps` |
| Compare with previous period | `true` | |
| Max sale rows | `1000` | 0 = no cap |

**Example: last 3 months of flat and terraced sales in SW11, with comps**

```json
{ "postcodes": ["SW11"], "propertyTypes": ["F", "T"], "dateFrom": "2026-06-01", "dateTo": "2026-08-31" }
```

**Example: 12 month comps only for three towns**

```json
{ "towns": ["BRISTOL", "LEEDS", "NOTTINGHAM"], "mode": "comps" }
```

### Output

Sale row:

```json
{
  "recordType": "sale",
  "price": 422975,
  "dateOfTransfer": "2026-08-27",
  "address": "FLAT A 38, BATH BUILDINGS, BRISTOL",
  "postcode": "BS6 5PU",
  "propertyType": "Flat/maisonette",
  "newBuild": false,
  "tenure": "Leasehold",
  "district": "CITY OF BRISTOL",
  "county": "CITY OF BRISTOL",
  "ppdCategory": "A (standard)"
}
```

Area comps row:

```json
{
  "recordType": "areaComps",
  "area": "SW11",
  "areaType": "postcodeDistrict",
  "propertyType": "Flat/maisonette",
  "periodFrom": "2026-06-01",
  "periodTo": "2026-08-31",
  "salesCount": 90,
  "medianPrice": 580000,
  "p25Price": 473750,
  "p75Price": 850000,
  "previousMedianPrice": 500000,
  "medianChangePct": 16.0,
  "salesCountChangePct": -36.2
}
```

A `RUN_SUMMARY` record in the default key value store has the periods, the latest data month, row counts and filters.

### Cost

You pay per event: one event per **sale row** and one per **area comps row**. Area comps for a few postcodes cost a few cents. See the Pricing tab for current prices.

### API

Run it from any language with the Apify API, for example:

```bash
curl -X POST "https://api.apify.com/v2/acts/seaf999ield~uk-land-registry-price-paid/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" -d '{"postcodes":["SW11"],"mode":"comps"}'
```

### Is it legal?

Yes. Price Paid Data is published by HM Land Registry as **open data under the Open Government Licence v3.0**. The actor downloads the official bulk files only; it does not use the PPD search app or SPARQL endpoint, which robots.txt asks bots not to crawl.

**Royal Mail condition:** the address fields include data from Royal Mail and Ordnance Survey. HM Land Registry says this address data may be used for personal and/or non commercial use, and commercially **only to display for the purpose of providing residential property price information services**. Any other commercial use of the addresses needs permission from Royal Mail (address.management@royalmail.com). You are responsible for your use of the data.

### FAQ

**How fresh is the data?** HM Land Registry publishes monthly, on the 20th working day, with sales registered up to the end of the previous month. Sales take weeks or months to be registered, so the **latest 2 to 3 months are incomplete**: compare counts with care.

**Does it cover Scotland or Northern Ireland?** No. Price Paid Data covers England and Wales only.

**What is category B?** Additional Price Paid entries: repossessions, buy to let purchases with a mortgage, and transfers to companies or other non private individuals. They're excluded by default so comps reflect standard market sales.

**Can I get older years?** Yes, any date range from 1995. Each extra year means another yearly file is read, so long ranges take longer.

### More

- **Weekly newsletter**, UK Industry & Bills: https://ukindustryandbills.substack.com

*Contains HM Land Registry data © Crown copyright and database right. This data is licensed under the Open Government Licence v3.0.*

# Actor input Schema

## `postcodes` (type: `array`):

Postcode area ("SW"), district/outcode ("SW11"), sector ("SW11 1") or full postcode ("SW11 1AA"). Each value is its own comps area.

## `towns` (type: `array`):

Post town as recorded by HM Land Registry, e.g. BRISTOL, LEEDS.

## `districts` (type: `array`):

E.g. CITY OF BRISTOL, WANDSWORTH, MANCHESTER.

## `counties` (type: `array`):

E.g. GREATER LONDON, WEST YORKSHIRE, KENT.

## `streets` (type: `array`):

Only keep sales whose street contains one of these strings.

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

YYYY-MM-DD. Leave empty for the last N months of available data.

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

YYYY-MM-DD. Leave empty for the latest month published by HM Land Registry.

## `months` (type: `integer`):

Length of the period when dateFrom is empty.

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

Leave empty for all types.

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

Filter new-build or established properties.

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

Freehold or leasehold.

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

Minimum sale price in pounds.

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

Maximum sale price in pounds.

## `includeAdditionalPricePaid` (type: `boolean`):

Category B = repossessions, buy-to-let, transfers to non-private individuals. Off = standard market sales only (category A).

## `mode` (type: `string`):

Sales rows, area comps rows, or both.

## `compareWithPreviousPeriod` (type: `boolean`):

Comps include the median and count for the same-length period immediately before, and the % change.

## `compsByPropertyType` (type: `boolean`):

Add a comps row per property type as well as all types.

## `sortBy` (type: `string`):

Order of sale rows.

## `maxResults` (type: `integer`):

Cap on sale rows (0 = no cap). Comps rows are always output.

## Actor input object example

```json
{
  "postcodes": [
    "SW11"
  ],
  "months": 12,
  "newBuild": "any",
  "tenure": "any",
  "includeAdditionalPricePaid": false,
  "mode": "salesAndComps",
  "compareWithPreviousPeriod": true,
  "compsByPropertyType": true,
  "sortBy": "dateDesc",
  "maxResults": 1000
}
```

# Actor output Schema

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

No description

## `summary` (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 = {
    "postcodes": [
        "SW11"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("seaf999ield/uk-land-registry-price-paid").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 = { "postcodes": ["SW11"] }

# Run the Actor and wait for it to finish
run = client.actor("seaf999ield/uk-land-registry-price-paid").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 '{
  "postcodes": [
    "SW11"
  ]
}' |
apify call seaf999ield/uk-land-registry-price-paid --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seaf999ield/uk-land-registry-price-paid"
        }
    }
}
```

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/sweVX3JZemfcbwg2M/builds/SjwLtw2lI5OCvFn0J/openapi.json