# England Heritage List - 400K Listed Buildings & Monuments (`j0401/uk-heritage-list`) Actor

The National Heritage List for England (OGL): 379,686 listed buildings, 20,003 scheduled monuments, parks and gardens, battlefields, protected wrecks and world heritage sites. Search by name, designation, grade or list entry; query by coordinate and radius; aggregate.

- **URL**: https://apify.com/j0401/uk-heritage-list.md
- **Developed by:** [Wenhao Yang](https://apify.com/j0401) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.03 / 1,000 england heritage designation records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## England Heritage List - 400K Listed Buildings & Monuments

The National Heritage List for England (NHLE), the statutory register kept by
Historic England: **401,774 designations** as of **26 October 2026** -
**379,686 listed building** designations, **20,003 scheduled monuments**,
**1,721 parks and gardens**, **47 battlefields**, **57 protected wreck
sites**, **27 world heritage sites**, plus building preservation notices and
certificates of immunity.

### Low cost

**From $0.00005 per record, down to $0.00003 at Gold.** Pay only for the
records you receive; the whole list stays searchable and you are never billed
for the scan behind it.

### What you get per designation

| field | meaning |
|---|---|
| `listEntry`, `name` | Historic England list entry number and designation name |
| `designation` | `listed-building`, `scheduled-monument`, `park-and-garden`, `battlefield`, `protected-wreck`, `world-heritage-site`, `building-preservation-notice` or `certificate-of-immunity` |
| `grade` | listed-building grade: `I`, `II*` or `II`; parks and gardens also carry a grade. Blank for the other designations |
| `designatedDate`, `amendedDate` | designation and last amendment dates where the layer publishes them |
| `areaHa` | designation area in hectares, where published |
| `nationalGridRef`, `easting`, `northing` | Ordnance Survey grid reference and coordinates |
| `latitude`, `longitude` | WGS84 coordinates - only the protected-wreck layer publishes them (57 records); use the grid reference for everything else |
| `distanceMetres` | straight-line metres from your coordinate to the designation's mapped geometry - 0 when the point is inside; most listed buildings are mapped as a small representative square (mode `near` only) |
| `captureScale`, `hyperlink` | source capture scale and the official list entry page |
| `refreshedDate` | snapshot date (search/aggregate) or query date (live `near`) |

### Search it

- **Name** - `name="Admiralty"` (substring).
- **Type** - `designation="scheduled-monument"`,
  `"park-and-garden"`, `"battlefield"`.
- **Grade** - `grade="I"`, `"II*"`, `"II"`.
- **Exact designation** - `listEntry="1066106"`.

### Example inputs

**Grade I listed buildings matching a word**

```json
{ "name": "church", "grade": "I", "maxResults": 100 }
```

**Scheduled monuments in the list**

```json
{ "designation": "scheduled-monument", "maxResults": 200 }
```

**What is designated near a coordinate (500 m)**

```json
{ "latitude": 51.5072, "longitude": -0.1276, "radiusKm": 0.5,
  "maxResults": 100 }
```

### Proximity queries

`mode=near` asks the Historic England service directly for designations whose
mapped footprint intersects the radius around your coordinate, and returns
the straight-line distance in metres from the published WGS84 geometry
(0 when the point falls inside it). This is the practical conveyancing /
insurance question: listed building, scheduled monument, park, battlefield
or wreck within a given distance. Radius 0.01-5 km. The only filter near
accepts is `designation`; name, grade and list-entry filters apply to
`mode=search`.

### Aggregate it

```json
{ "mode": "aggregate", "groupBy": "designation" }
```

`groupBy` = `designation` (default), `grade` or `captureScale`. Every row
carries `groupKey`, `groupCount`, `groupBy` and `totalMatched`.

The default (empty) run returns the designation summary. A search returns at
most 5,000 records per run.

### Scope and licence

This is the **statutory designation register**, not planning applications:
it tells you what is designated and where, not whether a planning application
exists. Coverage is **England**; Scotland, Wales and Northern Ireland keep
separate registers. Designation records carry no personal data.

Published by Historic England under the **Open Government Licence**, which
permits commercial reuse with attribution. Data source: the public National
Heritage List for England feature service.

# Actor input Schema

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

search = filter the list. aggregate = one row per group. near = live spatial query around a coordinate. warm = owner maintenance: rebuild the snapshot from the FeatureServer (no filters). Leave blank to auto-route: coordinates -> near, filters -> search, no filters -> aggregate.

## `name` (type: `string`):

Substring of the list entry name, case-insensitive (e.g. "church", "Admiralty").

## `designation` (type: `string`):

Exact designation type. Blank = all types. In mode=near this is the only filter allowed.

## `grade` (type: `string`):

Exact grade (I, II\* or II). Listed buildings and parks & gardens carry a grade; the other designations are blank.

## `listEntry` (type: `string`):

Exact Historic England list entry number, e.g. "1066106".

## `latitude` (type: `number`):

WGS84 latitude for mode=near (e.g. 51.5072). Use with longitude; name/grade/listEntry cannot be combined with near.

## `longitude` (type: `number`):

WGS84 longitude for mode=near (e.g. -0.1276). Use with latitude.

## `radiusKm` (type: `number`):

Search radius in kilometres for mode=near (default 0.5, maximum 5). Only used with latitude and longitude.

## `groupBy` (type: `string`):

designation -> designation type; grade -> listed-building grade; captureScale -> source capture scale. Blank defaults to designation.

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

Cap the number of search or near records pushed (0 = the default 50, maximum 5000). Aggregate returns every group.

## Actor input object example

```json
{
  "radiusKm": 0.5,
  "maxResults": 50
}
```

# Actor output Schema

## `recordsUrl` (type: `string`):

National Heritage List for England records - as JSON

## `datasetUrl` (type: `string`):

No description

## `runUrl` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("j0401/uk-heritage-list").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("j0401/uk-heritage-list").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 '{}' |
apify call j0401/uk-heritage-list --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,j0401/uk-heritage-list"
        }
    }
}
```

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/7599MoK9sZ5MYeBRw/builds/HRpgbcULACjRVsCSb/openapi.json