# England Planning Appeal Decision Signals (`starshaped_bullsnake/england-planning-appeal-decision-signals`) Actor

Track new and updated Planning Inspectorate appeal decisions for England.

- **URL**: https://apify.com/starshaped\_bullsnake/england-planning-appeal-decision-signals.md
- **Developed by:** [Starshape Tools](https://apify.com/starshaped_bullsnake) (community)
- **Categories:** Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 england planning appeal signals

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## England Planning Appeal Decision Signals

Tracks new decisions and later outcome/metadata changes in the official Planning Inspectorate Casework Database. Scope is **England only**, not the UK. It is for planning, development and local-government intelligence; it does not predict or guarantee outcomes.

Official source: [Planning Inspectorate Casework Database](https://www.gov.uk/government/publications/planning-inspectorate-appeals-database), official bulk XLSX and data notes. It is updated periodically (recent publication has varied between monthly and quarterly), so schedule monthly and do not expect faster freshness. Contains public sector information licensed under the Open Government Licence v3.0; attribution is required. The licence permits commercial reuse, persistent derived snapshots and redistribution of change records.

Signals: `NEW_APPEAL_DECISION`, `APPEAL_ALLOWED`, `APPEAL_DISMISSED`, `DECISION_UPDATED`, `DECISION_DATE_CHANGED`, and `DEVELOPMENT_TYPE_CHANGED`. The stable identity is the official `Reference`/`Case Number`; address and site names are never identity keys. The Actor maps physical workbook headers to internal canonical fields and tolerates unknown extra columns. Official fields such as authority, procedure, appellant, residential units, Green Belt, jurisdiction, recovery date and the costs-applied-for indicator are retained only when supplied and are never inferred. `Costs Applied For Indicator` is not a costs outcome, so this version does not emit `COSTS_DECISION`.

`{"mode":"sample","maxItems":100}` is the deterministic demonstration mode used by the example run. It creates representative England appeal decisions and passes them through the same production normalize, diff and filtering logic. It does not fetch the official workbook, open the production named key-value store, or read/write the production baseline. Live mode uses the official source and persistent snapshot.

The first live run stores a full baseline and emits zero. An unchanged live rerun emits zero. Processing is fetch → parse → normalize → validate → previous snapshot → diff → Dataset → `OUTPUT` summary → compressed snapshot commit. Fetch, schema, anomaly, Dataset or summary failures retain the old snapshot. `maxItems` caps Dataset output only and never truncates the stored live snapshot. Inputs: `mode`, `signalTypes`, `appealReferences`, `localPlanningAuthorities`, `decisions`, `developmentTypes`, `postcodePrefixes`, `baselineOnly`, `maxItems`.

Known limitations: the official file is a rolling selection, contains blanks and documented quality issues, omits in-progress/withdrawn/turned-away cases, and removed old rows are not treated as withdrawals. Source corrections can create update signals. The workbook is tens of MB; memory is dominated by XLSX parsing and the complete snapshot contains many thousands of compact records.

# Actor input Schema

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

Sample demonstrates England appeal signals without reading or changing the live snapshot.

## `signalTypes` (type: `array`):

Optional output signal types.

## `appealReferences` (type: `array`):

Official reference filter.

## `localPlanningAuthorities` (type: `array`):

Authority filter.

## `decisions` (type: `array`):

Decision filter.

## `developmentTypes` (type: `array`):

Development type filter.

## `postcodePrefixes` (type: `array`):

Postcode prefix filter.

## `baselineOnly` (type: `boolean`):

Store live baseline without signals.

## `maxItems` (type: `integer`):

Caps Dataset output only; never truncates a live snapshot.

## Actor input object example

```json
{
  "mode": "live",
  "baselineOnly": false,
  "maxItems": 1000
}
```

# Actor output Schema

## `OUTPUT` (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("starshaped_bullsnake/england-planning-appeal-decision-signals").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("starshaped_bullsnake/england-planning-appeal-decision-signals").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 starshaped_bullsnake/england-planning-appeal-decision-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,starshaped_bullsnake/england-planning-appeal-decision-signals"
        }
    }
}
```

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/UKRR7NfSadFgmErS3/builds/jmI9dAMlGmzcOHLGr/openapi.json