PlanningTrack API · Free beta

Integration recipes

Build the smallest workflow that answers your customer’s question.

Embed applications matching an address

Send authority and q to application search. Render summary cards, then retrieve details when someone opens a card. Include a council link and last-checked date. Label the result “Applications matching this address”, not “Complete property history”.

GET /v1/applications?authority=local-authority-oxo&q=12%20Example%20Road&limit=20

Display a decision and documents

Retrieve a returned application ID, use status.outcome for broad grouping, and retain original decision text. Read documentsAvailability before displaying current document links. Use timeline events when customers need published milestones and revisions.

Find recently received, approved projects

Combine authority, received-date bounds, and outcome=approved. Received-date filters describe submission timing, not the date a decision was made. Use the change feed to detect decisions made since your last check.

GET /v1/applications?authority=local-authority-oxo&receivedFrom=2026-01-01&receivedTo=2026-12-31&outcome=approved

Check a map viewport

Send bbox=west,south,east,north with WGS84 coordinates. Keep it within UK bounds and two degrees wide/high. Show that applications without source coordinates are excluded.

GET /v1/applications?authority=local-authority-oxo&bbox=-1.30,51.70,-1.20,51.80

Keep embedded records current

Poll /v1/changes daily and refresh only affected application IDs. Follow the checkpoint and initial-import recipe. Webhooks, bulk exports, and verified UPRN matching are not available in this release.