Kent
3,041 planning applications from Mid Kent, available as JSON over REST or through the MCP server. 6 fields are populated on at least 90% of records.
Measured across all 3,041 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 |
3,041 | 100.0% | |
description |
3,041 | 100.0% | |
reference |
3,041 | 100.0% | |
status |
3,027 | 99.5% | |
status_normalized |
3,027 | 99.5% | |
postcode |
2,866 | 94.2% |
| Field | Populated | Coverage | |
|---|---|---|---|
ward |
2,307 | 75.9% |
| Field | Populated | Coverage | |
|---|---|---|---|
applicant_name |
196 | 6.4% | |
application_type |
196 | 6.4% | |
decision_level |
195 | 6.4% | |
case_officer |
192 | 6.3% | |
officer_id |
192 | 6.3% | |
alternative_reference |
184 | 6.1% | |
standard_type |
175 | 5.8% | |
agent_id |
153 | 5.0% | |
agent_name |
153 | 5.0% | |
decision_date |
150 | 4.9% | |
decision |
130 | 4.3% | |
decision_normalized |
128 | 4.2% | |
agent_email |
27 | 0.9% | |
agent_company |
20 | 0.7% | |
agent_phone |
18 | 0.6% | |
appeal_decision |
1 | 0.0% | |
appeal_decision_normalized |
1 | 0.0% | |
development_type |
0 | 0.0% | |
easting |
0 | 0.0% | |
northing |
0 | 0.0% | |
officer_recommendation |
0 | 0.0% | |
property_id |
0 | 0.0% | |
received_date |
0 | 0.0% |
curl -H "X-Api-Key: $KEY" \ "https://ukplanningapi.co.uk/v1/applications?council_id=326&limit=5"
Council id for Mid Kent is 326.
Full endpoint reference →
500 requests a month, free. No card, no password.