Portfolio screening API
Screen a property portfolio for planning activity.
Batch full postcodes into thin planning-history flags, identify assets that need deeper review, and update a local portfolio index from the postcodes whose captured history changed.
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.
Batch-screen property postcodes
Usage is charged per valid unique postcode returned, not merely per HTTP request. Split batches to match your plan allowance.
POST /v1/property/flags
X-API-Key: YOUR_API_KEY
Content-Type: application/json
{"postcodes":["LS1 4AP","B1 1TB","EH1 1YZ"]}API authentication and response fields · Check council coverage
Move from national index to focused review.
The screening API returns compact flags rather than a bulk copy of planning records, keeping large asset workflows fast and commercially usable.
Batch valid postcodes
Submit full UK postcodes within the plan batch limit. Duplicates are collapsed and invalid entries are reported instead of silently ignored.
Triage captured history
Use applicationCount, hasRefusal, lastApplicationDate and lastDecisionDate to decide which assets enter deeper research.
Refresh deltas
Ask for postcodes whose planning history changed in a bounded recent window, then intersect them with your portfolio locally.
Retain interpretation
A planning flag is an operational signal, not an automated statement of property value, lending risk or legal status.
A practical portfolio pipeline
| Initial screen | Batch postcodes into compact flags and save the returned state against internal asset IDs. |
|---|---|
| Deep review | Retrieve detailed source-linked applications only for assets selected by your rules. |
| Incremental refresh | Consume changed postcodes, re-run flags and record which asset states actually moved. |
| Human decision | Apply your organisation's materiality, risk and action rules outside the API. |
Questions buyers ask
Does the endpoint return every planning record?
No. It deliberately returns compact postcode-level flags and dates. Use application search for source-linked detail.
Can I screen a national portfolio?
Yes, in bounded batches within your plan limits. Use changed-postcode deltas for ongoing maintenance instead of rebuilding every day.
Is hasRefusal a legal risk decision?
No. It means PlanWire captured at least one normalised refusal outcome for the postcode; your workflow decides relevance and materiality.
Related acquisition pages