Planning change feed
Keep a local planning index up to date.
Read bounded updated-record windows in stable cursor order, then combine them with signed webhooks and reconciliation so receiver downtime does not create silent gaps.
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.
Start a bounded change window
Use the cursor returned in meta.nextCursor for the next page. Keep all other selection filters unchanged.
GET /v1/applications?changed_since=2026-10-26T00%3A00%3A00Z&limit=100 X-API-Key: YOUR_API_KEY
Build for replay, overlap and idempotency.
updatedAt is a stored-record change timestamp. It is not council publication time, a decision-only stream, a deletion feed or an exactly-once guarantee.
Fix the window
Send changed_since with a timezone and retain the server-bounded changed_before value through every page.
Follow the cursor
Read meta.nextCursor with the same selection filters until it is null; do not switch to page offsets inside a change window.
Persist before advancing
Upsert records by id, finish every page successfully and only then move the durable polling checkpoint.
Overlap and reconcile
Overlap later polling windows to handle in-flight writes and replica lag, and periodically reconcile records your product tracks.
Choose the delivery mechanism
| Change-window polling | Ordered pull workflow for maintaining a local record index and controlling your own checkpoint. |
|---|---|
| Signed webhooks | Push delivery for captured events, with signature verification, retries and an ordered recovery stream. |
| Reconciliation | Periodic bounded searches or record reads to prove the local state still matches the source-backed API view. |
Questions buyers ask
Is updatedAt the council publication time?
No. It is when PlanWire last changed the stored record and can include maintenance or enrichment updates.
Is the feed exactly once?
No. Consumers must upsert idempotently, overlap windows and advance a checkpoint only after all pages are persisted.
Does the change feed include deletions?
Do not treat it as a deletion feed. Use the documented record state and your own reconciliation requirements.
Related acquisition pages