APPLICATION FOR A SINGLE STOREY OUTBUILDING WITH SOLAR PANELS
9 Toynbee Road, Raynes Park, Merton, SW20 8SH
Planning application coverage
PlanWire tracks 4,032 planning records for London Borough of Merton, spanning 19 Dec 2024 to 31 Aug 2026. Search the underlying applications and source links through one monitored API.
Live near London Borough of Merton? 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
4,032
History begins
19 Dec 2024
Latest dated app
6 days ago
Source checked
today
Latest cached dated application: 31 Aug 2026. Use API date filters for exact recent counts.
Recent application preview
Five recent dated applications. API responses include fuller machine-readable fields and pagination.
9 Toynbee Road, Raynes Park, Merton, SW20 8SH
4 Allgood Close, Morden, Surrey, Merton, SM4 4PA
25 Heaton Road, Mitcham, Surrey, Merton, CR4 2BW
8 Friday Road, Mitcham, Merton, CR4 3JQ
6 Manship Road, Mitcham, Surrey, Merton, CR4 2AY
Local record profile
London Borough of Merton is a focused local planning history, with 4,032 records tracked. The public record spans 2024 to 2026, so the page is useful for recent monitoring as well as historic checks around sites and addresses.
Authority context
London Borough of Merton is an urban London borough, where local planning records are often used to monitor dense residential, commercial and neighbourhood change at street level.
Recent activity pattern
London Borough of Merton has a cached latest dated application of 6 days ago. Use API date filters for exact recent counts when sizing local monitoring or alerting workflows.
Monitoring fit
London Borough of Merton 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
Latest dated application is 6 days ago.
Completeness signal
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=merton for application records with an API key.