Kent
4,785 planning applications from Tunbridge Wells, available as JSON over REST or through the MCP server. 6 fields are populated on at least 90% of records.
Measured across all 4,785 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,785 | 100.0% | |
description |
4,785 | 100.0% | |
received_date |
4,785 | 100.0% | |
reference |
4,785 | 100.0% | |
status |
4,737 | 99.0% | |
status_normalized |
4,737 | 99.0% |
| Field | Populated | Coverage | |
|---|---|---|---|
postcode |
4,298 | 89.8% | |
ward |
3,272 | 68.4% |
| Field | Populated | Coverage | |
|---|---|---|---|
applicant_name |
198 | 4.1% | |
application_type |
198 | 4.1% | |
case_officer |
194 | 4.1% | |
decision_level |
198 | 4.1% | |
officer_id |
194 | 4.1% | |
standard_type |
183 | 3.8% | |
alternative_reference |
179 | 3.7% | |
agent_id |
154 | 3.2% | |
agent_name |
154 | 3.2% | |
agent_company |
149 | 3.1% | |
decision_date |
150 | 3.1% | |
decision |
136 | 2.8% | |
decision_normalized |
134 | 2.8% | |
agent_email |
24 | 0.5% | |
agent_phone |
12 | 0.3% | |
appeal_decision |
0 | 0.0% | |
appeal_decision_normalized |
0 | 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% |
curl -H "X-Api-Key: $KEY" \ "https://ukplanningapi.co.uk/v1/applications?council_id=448&limit=5"
Council id for Tunbridge Wells is 448.
Full endpoint reference →
500 requests a month, free. No card, no password.