UK Planning Applications Feed (Apify Actor)

Search UK planning applications by council, postcode radius, keyword and date range: reference, address, description, status, dates, link and lat/lng. Data from UK PlanIt, no key. Runs as an Apify Actor, callable from MCP clients via the Apify MCP server (https://mcp.apify.com/?actors=pennydata/uk-planning-applications-feed).

View on apify.com

Hosted MCP Server

npx add-mcp 'https://mcp.apify.com/?actors=pennydata/uk-planning-applications-feed'

Installs into Claude Code, Codex, Cursor and more

Documentation

UK Planning Applications Feed - Council Planning Data, $4/1K (`pennydata/uk-planning-applications-feed`) Actor

Search UK planning applications by council, postcode radius, keyword and date range: reference, address, description, status, dates, link and lat/lng. Data from UK PlanIt, no key.

URL: https://apify.com/pennydata/uk-planning-applications-feed.md
Developed by: Penny Data (community)
Stats: 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
User rating: No ratings yet

Pricing

from $4.00 / 1,000 planning application returneds

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 section below.

Each client library has reference documentation the quickstart does not restate: JavaScript/TypeScript (npm install apify-client) and Python (pip install apify-client).

README

UK Planning Applications Feed

Search UK planning applications by council, postcode radius, keyword and date range. Returns one flat row per application: reference, address, description, type, status, dates, lat/lng and links. Pay per application, no API key.

What you get

Field	Example
`reference`	`26/02010/COND`
`authority`	`Doncaster`
`address`	`Land Side Of Central Garage High Street Carcroft Doncaster DN6 8DP`
`description`	`Former partial approval for condition 7 ...`
`appType`, `appState`, `appSize`	`Conditions`, `Undecided`, `Small`
`startDate`, `dateReceived`, `decidedDate`	`2026-10-21`, `2026-10-21`, `null`
`lat`, `lng`	`53.583057`, `-1.1813`
`url`, `councilUrl`	PlanIt page and the council's own page

Applicant and agent names are not included (the source does not store them).

Input example

{
  "authority": "Doncaster",
  "search": "extension or \"change of use\"",
  "recentDays": 30,
  "appState": "Undecided",
  "maxResults": 100
}

authority: council / planning area name (Doncaster, Camden, Leeds ...). Empty = whole UK, then set postcode or search.
postcode + radiusKm: radius search around a postcode (1-20 km).
search: description keywords. Quote phrases, or between alternatives, leading - to exclude.
recentDays or startDate / endDate: filter on application start date.
appState, appType: optional filters. maxResults: 1-5000, default 100.

Pricing

Pay per event: $0.004 per application returned ($4 per 1,000) plus $0.001 per run start. Error rows are not charged.

Speed

The source asks clients to leave 60 seconds between requests, and the actor does. Up to 300 applications come back in one request (a few seconds); every further 300 add about a minute.

Source

Data from UK PlanIt by Andrew Speakman, which collects public planning records from local authority websites. PlanIt states the data may be used for anything, with no attribution required; credit is given anyway. This actor is not affiliated with PlanIt. Records are public register information; plans and drawings on council sites remain the applicants' copyright and are only linked, never copied. PlanIt is a free hobby service run on a best-efforts basis, so availability is not guaranteed.

Built with AI help (Claude).

Actor input Schema

`authority` (type: `string`):

UK PlanIt area name, for example Doncaster, Camden or Leeds. Leave empty to search the whole UK (then use a postcode or keyword).

`search` (type: `string`):

Text searched in the application description. Quote phrases, use 'or' between alternatives and a leading dash to exclude, for example "change of use" or extension -conservatory.

`postcode` (type: `string`):

UK postcode used as the centre of a radius search, for example SW1A 2AA.

`radiusKm` (type: `integer`):

Search radius around the postcode, in km (1-20).

`recentDays` (type: `integer`):

Only applications that started within this many days. Ignored when Start date or End date is set.

`startDate` (type: `string`):

YYYY-MM-DD. Applications whose start date is on or after this day.

`endDate` (type: `string`):

YYYY-MM-DD. Applications whose start date is on or before this day.

`appState` (type: `string`):

Filter by status.

`appType` (type: `string`):

Filter by type.

`maxResults` (type: `integer`):

Maximum applications to return (1-5000). Each 300 results need one request to PlanIt, spaced 60 seconds apart as PlanIt asks.

Actor input object example

{
  "authority": "Doncaster",
  "radiusKm": 2,
  "recentDays": 14,
  "appState": "",
  "appType": "",
  "maxResults": 100
}

Actor output Schema

`items` (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

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 = {
    "authority": "Doncaster"
};

// Run the Actor and wait for it to finish
const run = await client.actor("pennydata/uk-planning-applications-feed").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

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 = { "authority": "Doncaster" }

# Run the Actor and wait for it to finish
run = client.actor("pennydata/uk-planning-applications-feed").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

echo '{
  "authority": "Doncaster"
}' |
apify call pennydata/uk-planning-applications-feed --silent --output-dataset

MCP server setup

{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pennydata/uk-planning-applications-feed"
        }
    }
}

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/a5bjWfhFdBOLKEAKR/builds/jSClJdUZHI5VeIVol/openapi.json

UK Planning Applications Feed (Apify Actor)

Hosted MCP Server

Documentation

UK Planning Applications Feed - Council Planning Data, $4/1K (pennydata/uk-planning-applications-feed) Actor

Pricing

What's an Apify Actor?

How to integrate an Actor?

README

UK Planning Applications Feed

What you get

Input example

Pricing

Speed

Source

Actor input Schema

authority (type: string):

search (type: string):

postcode (type: string):

radiusKm (type: integer):

recentDays (type: integer):

startDate (type: string):

endDate (type: string):

appState (type: string):

appType (type: string):

maxResults (type: integer):

Actor input object example

Actor output Schema

items (type: string):

API

JavaScript example

Python example

CLI example

MCP server setup

OpenAPI specification

UK Planning Applications Feed - Council Planning Data, $4/1K (`pennydata/uk-planning-applications-feed`) Actor

`authority` (type: `string`):

`search` (type: `string`):

`postcode` (type: `string`):

`radiusKm` (type: `integer`):

`recentDays` (type: `integer`):

`startDate` (type: `string`):

`endDate` (type: `string`):

`appState` (type: `string`):

`appType` (type: `string`):

`maxResults` (type: `integer`):

`items` (type: `string`):