Property intelligence API
Build property intelligence around real planning change.
Combine source-linked planning applications and decisions with UPRN identity, EPC context, sold-price summaries, constraints and market evidence where the underlying records support a safe join.
Product and property teams use PlanWire when they need source-linked planning data without maintaining council-source integrations, with UPRN where available for property-dataset joins. Source-linked application records, freshness metadata and webhook workflows. Check current council-level coverage and history for your integration. Monthly billing with no minimum term.
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.
Read one enriched application
A paid single-record read returns property context only where the application has a supported identity or spatial join. Treat every nested dataset as optional.
GET /v1/applications/2ad3a854-64a8-4ccf-8a27-fc4a88b1a3ad
X-API-Key: YOUR_API_KEYAPI authentication and response fields · Check council coverage
One planning-led layer for property products.
PlanWire starts with activity published by planning authorities, then exposes the property context your product can use without pretending every field exists on every record.
Find planning activity
Search applications by council, postcode, UPRN, dates, status, decision outcome, keywords or coordinate radius.
Resolve the property
Use source-native or matched UPRN identity and match provenance where available, with nulls preserved when a safe join cannot be made.
Add decision context
Retrieve normalised outcomes, source decision text and supplied decision dates without treating a permission as proof that construction started.
Enrich the record
Single-application reads can add EPC facts, HMLR price-paid summaries and known planning constraints where PlanWire has a supported join.
Screen an index
Batch property flags answer whether a postcode has captured planning activity or refusals without returning the complete application corpus.
Operate continuously
Use updated-record cursors, signed webhooks, source links and council freshness metadata for a recoverable production workflow.
The property-intelligence layers
| Planning activity | Applications, captured changes, available decisions, original references and source links. |
|---|---|
| Property identity | UPRN plus match method and confidence where a safe identity link is available. |
| Property context | Optional EPC, price-paid and constraint context for supported single-record reads. |
| Operational evidence | Council freshness, record timestamps, webhook recovery and explicit source failure states. |
Questions buyers ask
Is PlanWire a general property database?
PlanWire is planning-led property intelligence. It combines planning activity with selected property context where supported; it does not claim every ownership, title, contact or risk dataset.
Does every application include a UPRN and enrichment?
No. UPRN, EPC, price-paid and constraint fields depend on source availability and safe matching. Missing context remains null rather than being guessed.
Can we use the data in our property product?
Yes, subject to the published terms, your plan limits and the caching or redistribution model you require. Discuss high-volume or licensed delivery before implementation.
Related acquisition pages