South London
4,316 planning applications from Kingston upon Thames, available as JSON over REST or through the MCP server. 4 fields are populated on at least 90% of records.
Measured across all 4,316 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 |
4,316 | 100.0% | |
description |
4,316 | 100.0% | |
reference |
4,316 | 100.0% | |
postcode |
4,173 | 96.7% |
| Field | Populated | Coverage | |
|---|---|---|---|
ward |
3,399 | 78.8% | |
received_date |
2,429 | 56.3% | |
application_type |
2,424 | 56.2% | |
case_officer |
2,420 | 56.1% | |
officer_id |
2,420 | 56.1% | |
applicant_name |
2,414 | 55.9% | |
alternative_reference |
2,326 | 53.9% | |
status |
2,296 | 53.2% | |
status_normalized |
2,296 | 53.2% | |
agent_id |
2,155 | 49.9% | |
agent_name |
2,155 | 49.9% | |
decision |
2,043 | 47.3% | |
decision_date |
2,039 | 47.2% | |
decision_level |
2,034 | 47.1% | |
decision_normalized |
1,885 | 43.7% |
| Field | Populated | Coverage | |
|---|---|---|---|
standard_type |
215 | 5.0% | |
property_id |
77 | 1.8% | |
agent_company |
33 | 0.8% | |
agent_email |
1 | 0.0% | |
agent_phone |
0 | 0.0% | |
appeal_decision |
2 | 0.0% | |
appeal_decision_normalized |
2 | 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=135&limit=5"
Council id for Kingston upon Thames is 135.
Full endpoint reference →
500 requests a month, free. No card, no password.