Planning webhooks

Turn planning updates into product events.

Use PlanWire webhooks to send matching planning activity into your backend for alerts, queues, maps, CRMs, monitoring and customer notifications.

Developers use PlanWire when they need live planning data without maintaining council-source integrations, with UPRN where available for property-dataset joins. 18.3M+ planning application records, 375 live planning authorities, source links, freshness metadata and webhook-ready workflows.

Example webhook payload

Webhook events point you to the record; the API can then fetch the latest full representation.

{ "event": "application.updated", "council": "reading", "reference": "241234", "firstSeenAt": "2026-09-03T07:05:00Z" }

Webhook delivery for planning workflows.

Polling can work. Webhooks are cleaner when planning updates need to trigger customer or operational workflows.

Signed events

Receive planning application update events in your backend and verify delivery before processing.

Filtered delivery

Design webhook filters around councils, areas, keywords and application workflows instead of moving every record manually.

Fallback polling

Use the REST API to reconcile records, retry failed jobs and inspect application details after an event arrives.

Source context

Keep source URLs and council references available for users who need to verify the official record.

When to use webhooks

Planning alertsNotify users when a watched area or matching application changes.
CRM and lead queuesPush relevant applications into sales, service or research workflows.
Data syncKeep a product database current without running broad repeated searches.

Questions buyers ask

Can webhooks power planning alerts?

Yes. Webhooks can support alert products where matching planning activity should trigger downstream notifications.

Do I still need the REST API?

Usually yes. Webhooks are best paired with API reads for reconciliation, backfills and record details.

Can I start with one area?

Yes. Teams can start with a small set of areas or filters, then expand as usage grows.

Related acquisition pages

Keep comparing planning-data options.