Property planning history
Add captured planning history to a property workflow.
Screen postcodes for captured applications and refusals, then retrieve source-linked planning records for the properties that need a deeper review.
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.
Screen two property postcodes
Property flags are paid and deliberately thin. They identify where deeper research may be useful without returning the underlying corpus.
POST /v1/property/flags
X-API-Key: YOUR_API_KEY
Content-Type: application/json
{"postcodes":["SW1A 1AA","M1 1AE"]}
Use a two-stage property-history workflow.
A thin screening call keeps large property indexes efficient; detailed application search provides the evidence only where it is needed.
Screen postcodes in batches
POST postcode batches to property flags and receive application count, refusal presence and latest captured application and decision dates.
Open the matching history
Query applications by full postcode or UPRN and retain references, dates, descriptions, decisions and public source links.
Refresh only changed areas
Use the changed-postcode endpoint to update a local index without re-submitting an entire national portfolio.
State the limitation
An empty response is not an official planning-history certificate or proof that no relevant record exists.
Choose the right depth
| Property flags | Fast batch screening by postcode: counts, refusal flag and latest captured dates. |
|---|---|
| Application search | Detailed source-linked records for a postcode, UPRN, council or known reference. |
| Formal search | Use the appropriate authority, conveyancing and professional checks for a legally relied-on conclusion. |
Questions buyers ask
Can I check planning history by postcode?
Yes. Use full-postcode application search for records or the paid batch flags endpoint for thin portfolio screening.
Is a postcode the same as a property?
No. Several properties may share a postcode. Use UPRN where available when your workflow requires property-level identity.
Can an empty result prove there is no planning history?
No. Coverage, source availability, historic depth and address matching vary, so empty results must remain qualified.
Related acquisition pages