Planning applications API
Application references, addresses, dates, decisions and source links in JSON. Add postcode search, radius search and signed webhooks to your product.
Live-data plans from £49/month + VAT for property products, application monitoring and CRM integrations. Check coverage and freshness for your councils before choosing a plan.
Free keys are limited to historical/sample data. Current data and ongoing monitoring require a paid plan. Get a sample key to test the API shape.
Inspect a planning record
One recent indexed record, selected public fields. No key required.
Loading sample...
Samples are cached for up to five minutes. Source-check time is separate from application dates and API availability. Planning activity is not proof of construction starting.
Make a council-scoped request
Keep your key on your server or in a local environment variable, never in published browser code. Choose a council ID from the coverage directory. Free keys return a limited preview.
curl 'https://api.planwire.io/v1/applications?council=richmond-thames&limit=5' \
-H "X-API-Key: $PLANWIRE_API_KEY"Narrow the application date window
curl 'https://api.planwire.io/v1/applications?council=richmond-thames&date_from=2026-09-01&date_to=2026-09-08&limit=5' \
-H "X-API-Key: $PLANWIRE_API_KEY"These dates are an example window, not a rolling freshness claim. Application dates do not establish when building work began. Read the filter semantics and response schema before designing incremental imports.
Working Node.js example and tests: one council-scoped request, no dependencies, a bounded timeout and no credentials in URLs.
Handle the response before scaling
Check HTTP status before parsing records. Keep source URLs and council references alongside your stored results, handle missing fields, and respect pagination and plan limits. A 401 indicates an authentication problem; an empty successful response is different from a failed request.
Use the first-request guide, evaluate data quality and coverage, or compare UK integration approaches.
Search by postcode or distance
An exact postcode, an outward code and a circle around coordinates answer different questions. Follow the postcode and radius search guide with JavaScript and Python examples to select the correct endpoint and understand missing-location and result-limit behavior.
For a council-first integration, start with searching UK planning applications in Python. Both guides keep credentials in your server environment and distinguish sample records from live access.
Choose live planning data for your product.
Developer starts at £49/mo + VAT; Production is £199/mo + VAT. Compare request allowances and webhook limits against your workload. See customer integrations.