Planning application coverage

Leeds City Council planning applications and history.

PlanWire tracks 241k planning records for Leeds City Council, spanning 2 Jan 1990 to 4 Sept 2026. Search the underlying applications and source links through one monitored API.

Get planning alerts for Leeds City Council Get this data via API Coverage overview
planning applications API planning alerts API planning data API postcode planning data API planning webhooks proptech planning API planning application leads API MCP planning data server

Live near Leeds City Council? Set up a planning alert and get an email when an application is submitted close to your postcode. Building a product instead? The same records are available through the API.

Records tracked

241k

History begins

2 Jan 1990

Latest dated app

2 days ago

Source checked

today

Latest cached dated application: 4 Sept 2026. Use API date filters for exact recent counts.

Recent application preview

Latest public records from Leeds City Council

Five recent dated applications. API responses include fuller machine-readable fields and pagination.

Recent application preview is temporarily unavailable for Leeds City Council; aggregate coverage and API metadata remain available.

Local record profile

Leeds City Council is a high-volume local planning history, with 241k records tracked. The public record spans 1990 to 2026, so the page is useful for recent monitoring as well as historic checks around sites and addresses.

Authority context

Leeds City Council is a city planning authority, so recent applications can be a useful signal for housing, commercial premises, infrastructure and regeneration activity.

Recent activity pattern

Leeds City Council has a cached latest dated application of 2 days ago. Use API date filters for exact recent counts when sizing local monitoring or alerting workflows.

Monitoring fit

Leeds City Council has cached latest-date coverage in this public summary. API users can combine council filters, date filters and freshness metadata for exact operational checks.

Freshness status

Fresh in last 7 days

Latest dated application is 2 days ago.

Completeness signal

No open source caveat

Latest checked, latest dated application and API source metadata are published with the council record. Document metadata is exposed where the source supplies it.

Machine-readable access

Use GET /v1/councils for coverage metadata and GET /v1/applications?council_id=leeds for application records with an API key.

Try this exact query Query docs