Planning and land teams · Captured product example
Which site checks still need resolving?
London planning records alongside a failed designation check: a reason to investigate, not a clean bill of health.
Editorial interpretation of production responses captured on 6 September 2026. This is not a newly run workflow or a customer case study.
The decision to investigate
Is the planning evidence sufficient to prioritise a site for deeper appraisal?
What the captured evidence shows
The captured SE22 8HN query returns Southwark planning records sourced from the GLA Datahub, including references and decisions. Some decision dates and application links are missing. The separate designation request failed with HTTP 502.
Proposed next investigation
Confirm the exact site and application documents with Southwark, resolve missing dates and repeat the designation check before assessing constraints. Nearby applications are context, not consent for the subject site.
Limits of this example
These are separate captured calls, not a completed site appraisal. A failed check remains unknown. London planning history does not establish equivalent coverage elsewhere, and a shortlist does not establish availability or development consent.
Cost and reproducibility
Each capture below shows the request, date and recorded charge when available. These excerpts do not measure an end-to-end workflow cost or research time. Supporting address, property, comparable and ownership calls may add charges; an unknown charge is not zero.
Responses are trimmed historical records. Source observation dates differ from capture dates. Product version is only known where recorded in the response. Re-run and review the complete result before relying on it.
planning_applications
POST /v1/planning/applications {"postcode":"SE22 8HN"}{
"country": "UK",
"query": {
"postcode": "SE22 8HN"
},
"data": {
"data": {
"postcode": "SE22 8HN",
"lpa_name": "Southwark",
"planning_search_url": "https://planning.southwark.gov.uk/online-applications/search.do?action=advanced",
"applications": [
{
"reference": "17/AP/2957",
"address": "16A 16A LORDSHIP LANE SE22 8HN",
"proposal": "Conversion of upper floors of building from a 5-bed flat to create 1 x 2-bed flat and 1 x 3-bed flat, including construction of a rear dormer roof extension an…",
"status": "Completed",
"decision": "Approved",
"received_date": null,
"decided_date": null,
"url": null,
"lpa_code": "SWK",
"application_type": "Full planning permission",
"distance_m": 1.9,
"source": "gla_datahub"
},
{
"reference": "23/AP/0833",
"address": "16 Lordship Lane SE22 8HN",
"proposal": "Replacement of existing timber shopfront with glass and steel frame shopfront.\r",
"status": "Approved",
"decision": "Approved",
"received_date": null,
"decided_date": null,
"url": null,
"lpa_code": "SWK",
"application_type": "Full planning permission",
"distance_m": 2.3,
"source": "gla_datahub"
},
{
"reference": "23/AP/1974",
"address": "18 Flat B Lordship Lane SE22 8HN",
"proposal": "Rear dormer roof extension and roof lights to the front roof slope.",
"status": "Approved",
"decision": "Approved",
"received_date": null,
"decided_date": null,
"url": null,
"lpa_code": "SWK",
"application_type": "Full planning permission",
"distance_m": 2.7,
"source": "gla_datahub"
},
"… 17 more"
],
"result_count": 20,
"source": "warehouse",
"execution_time_ms": 288.8226509094238
}
},
"credits_charged": 0
}A real response, captured from production and trimmed: arrays to three items, long strings shortened, volatile keys dropped.
planning_designations
POST /v1/planning/designations {"postcode":"SE22 8HN"}{
"error": "HTTP 502",
"detail": "The origin web server returned an invalid or incomplete response to Cloudflare. This typically indicates the origin is overloaded or misconfigured."
}The call failed with these arguments; the status and message are shown rather than an invented body.
Test it against a property you know.
Bring a real decision and compare the evidence with your current research process.
Bring a property to a demo