# Sold house prices by postcode for lending and valuation teams

**Use case:** 

Pull recent HM Land Registry sold prices for a list of UK postcodes or streets in bulk: price, date, property type, tenure and new-build flag. Use it for secured lending and affordability checks, property-backed underwriting, valuations or proptech CRMs, and schedule it monthly via API, Zapier, Make or n8n. Demo uses one Leeds postcode area.

## Input

```json
{
  "searches": [
    {
      "postcode": "LS6 1AA"
    }
  ],
  "maxSalesPerSearch": 25
}
```

## Output

```json
{
  "type": {
    "label": "sale or summary",
    "format": "string"
  },
  "price": {
    "label": "Price paid",
    "format": "integer"
  },
  "date": {
    "label": "Completion date",
    "format": "string"
  },
  "address": {
    "label": "Address",
    "format": "string"
  },
  "postcode": {
    "label": "Postcode",
    "format": "string"
  },
  "propertyType": {
    "label": "Property type",
    "format": "string"
  },
  "tenure": {
    "label": "Tenure",
    "format": "string"
  },
  "newBuild": {
    "label": "New build",
    "format": "boolean"
  },
  "medianPrice": {
    "label": "Median price",
    "format": "number"
  },
  "ok": {
    "label": "Succeeded",
    "format": "boolean"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The UK House Prices - Land Registry Price Paid Actor is ready to run with the inputs already set for "Sold house prices by postcode for lending and valuation teams". [Sign up or log in](https://console.apify.com/create-task-from-example/yDDOZ1sOOutSwVCFH) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Sold house prices by postcode for lending and valuation teams" task

The UK House Prices - Land Registry Price Paid Actor will start running based on the input automatically. You can also change all the input fields, like searches and max sales per search, to match your specific use case.

### 3. Receive the "Sold house prices by postcode for lending and valuation teams" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as sale or summary, price paid, completion date, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Sold house prices by postcode for lending and valuation teams" task via API](https://apify.com/sterlingverify/uk-house-prices.md).

## About this Actor

This example demonstrates how to use [UK House Prices - Land Registry Price Paid](https://apify.com/sterlingverify/uk-house-prices.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/sterlingverify/uk-house-prices.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

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 full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/sterlingverify/uk-house-prices.md

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`).