UK Council Planning Applications Monitor
Pricing
from $50.00 / 1,000 application founds
UK Council Planning Applications Monitor
Monitor newly validated, decided, or updated planning applications across selected UK council portals (Idox PublicAccess, Northgate Planning Explorer). HTTP-only; designed for scheduled runs with onlyNew dedupe.
Pricing
from $50.00 / 1,000 application founds
Rating
0.0
(0)
Developer
Siddhant
Maintained by CommunityActor stats
0
Bookmarked
4
Total users
2
Monthly active users
14 hours ago
Last modified
Categories
Share
Monitor newly validated, decided, or updated planning applications across selected UK council portals. Returns a normalized, alert-ready record per application.
Designed for scheduled runs: pair with Apify Schedules + an Apify Webhook (or Zapier/Make integration) to get notified when new applications appear. Pay-per-event pricing means you only pay for the applications surfaced.
Supported Councils
Pass the council ID (left column) in the councils input. 21 councils across two portal types are currently supported.
Idox Public Access (20)
| Council ID | Council |
|---|---|
woking | Woking Borough Council |
westminster | Westminster City Council |
brent | Brent London Borough Council |
isle-of-wight | Isle of Wight Council |
tendring | Tendring District Council |
durham | Durham County Council |
north-norfolk | North Norfolk District Council |
north-tyneside | North Tyneside Council |
leeds | Leeds City Council |
bristol | Bristol City Council |
cornwall | Cornwall Council |
glasgow | Glasgow City Council |
croydon | London Borough of Croydon |
barnet | London Borough of Barnet |
nottingham | Nottingham City Council |
southwark | London Borough of Southwark |
greenwich | Royal Borough of Greenwich |
enfield | London Borough of Enfield |
wakefield | Wakefield Council |
aberdeen | Aberdeen City Council |
Northgate Planning Explorer (1)
| Council ID | Council |
|---|---|
birmingham | Birmingham City Council |
failOnCouncilError (boolean, default false) — when false, a single failing council records a {status:'failed',error} entry in the run summary and the run continues to remaining councils. When true, the run fails on the first council error.
More councils are added on request — most UK councils run Idox Public Access or Northgate Planning Explorer, both of which are already supported, so adding one is typically a small configuration change.
Scheduling tip for Westminster: Westminster's weekly-list form exposes a 4-week rolling window of recent applications. If you're using
onlyNew: trueto track new applications, run at least every 4 weeks (a weekly schedule is well within bound). Brent and Woking have longer windows (52 and 16 weeks respectively).
Input
| Field | Type | Default | Description |
|---|---|---|---|
councils | string[] | required | Council IDs (e.g. "woking") or full portal URLs. |
dateMode | enum | validated | One of validated, decided, updated. |
dateFrom | string (YYYY-MM-DD) | 7 days ago | Start of search window. |
dateTo | string (YYYY-MM-DD) | today | End of search window. |
keywords | string[] | [] | Case-insensitive match against proposal/description/address. |
postcodes | string[] | [] | Outward (e.g. GU21) or full postcode filters where the portal supports them. |
maxResultsPerCouncil | integer | 100 | Cap per council per run. |
includeDetails | boolean | true | Fetch detail pages to enrich status/ward/documents. |
includeDocuments | boolean | false | Surface document-list metadata (title, type, date, URL). Documents are never downloaded. |
stateKey | string | — | Optional key enabling monitoring mode (onlyNew, firstSeenAt, lastSeenAt). |
onlyNew | boolean | false | When true, output only applications not seen in prior runs for the same stateKey. |
Example: weekly Woking watch
Output
Each application is one dataset record. Key fields:
| Field | Description |
|---|---|
councilId / councilName / portalType | Source identifiers. |
applicationRef | Council's application reference (e.g. PLAN/2026/0042). |
address / postcode | Site location. |
proposal | Description of works. |
applicationType / status / decision | Application category and current state. |
receivedDate / validatedDate / decisionDate | Key dates. |
ward / parish / caseOfficer | Local context. |
documents | Document-list metadata (title, type, date, URL) — only when includeDocuments: true. Documents are never downloaded. |
firstSeenAt / lastSeenAt / isNew | Monitoring-mode tracking (only populated when stateKey is set). |
detailUrl / documentsUrl | Source-verifiable links back to the council portal. |
Notes
- Document content is never downloaded. Only metadata (title, type, date, URL) is surfaced.
- Public comments are not scraped (personal-data risk).
applicantName/agentNameare returned only when the council exposes them publicly on detail pages.
Reliability
- Transient network failures retry automatically with exponential backoff.
- Per-council error isolation: a single failing council does not fail the whole run unless
failOnCouncilErroris true. The summary records each council's status individually.
Roadmap
- More Northgate Planning Explorer councils (the adapter is live — Birmingham is the first; Wandsworth needs detail-page enrichment for dates/decision before it ships).
- Additional Idox and Northgate councils by request.
