Planning application coverage

Lewes District Council planning applications and history.

PlanWire tracks 46.5k planning records for Lewes District Council, spanning 1 Jan 1990 to 2 Sept 2026. Search the underlying applications and source links through one monitored API.

Get planning alerts for Lewes District 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 Lewes District 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

46.5k

History begins

1 Jan 1990

Latest dated app

4 days ago

Source checked

2 days ago

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

Recent application preview

Latest public records from Lewes District Council

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

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

Local record profile

Lewes District Council is a substantial local planning history, with 46.5k 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

Lewes District Council is a district planning authority, where PlanWire helps product teams avoid one-off portal integrations for local application monitoring.

Recent activity pattern

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

Monitoring fit

Lewes District 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 4 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=lewes for application records with an API key.

Try this exact query Query docs