South London
128 planning applications from Kingston, available as JSON over REST or through the MCP server. 5 fields are populated on at least 90% of records.
We hold only 128 applications here. Treat an absent record as "not published to us", never as "no such application".
Measured across all 128 records. This is what
is actually filled in, not what the council's portal offers — ask
get_council_fields for the same numbers from an MCP client.
| Field | Populated | Coverage | |
|---|---|---|---|
address |
128 | 100.0% | |
description |
128 | 100.0% | |
reference |
128 | 100.0% | |
ward |
126 | 98.4% | |
postcode |
124 | 96.9% |
| Field | Populated | Coverage | |
|---|---|---|---|
received_date |
83 | 64.8% | |
applicant_name |
82 | 64.1% | |
application_type |
82 | 64.1% | |
case_officer |
82 | 64.1% | |
officer_id |
82 | 64.1% | |
standard_type |
82 | 64.1% | |
alternative_reference |
79 | 61.7% | |
agent_id |
73 | 57.0% | |
agent_name |
73 | 57.0% | |
decision_date |
72 | 56.2% | |
decision |
71 | 55.5% | |
status |
69 | 53.9% | |
status_normalized |
69 | 53.9% | |
decision_normalized |
65 | 50.8% | |
property_id |
57 | 44.5% | |
agent_company |
19 | 14.8% | |
agent_email |
13 | 10.2% |
| Field | Populated | Coverage | |
|---|---|---|---|
agent_phone |
0 | 0.0% | |
appeal_decision |
0 | 0.0% | |
appeal_decision_normalized |
0 | 0.0% | |
decision_level |
0 | 0.0% | |
development_type |
0 | 0.0% | |
easting |
0 | 0.0% | |
northing |
0 | 0.0% | |
officer_recommendation |
0 | 0.0% |
curl -H "X-Api-Key: $KEY" \ "https://ukplanningapi.co.uk/v1/applications?council_id=303&limit=5"
Council id for Kingston is 303.
Full endpoint reference →
500 requests a month, free. No card, no password.