Inner London
7,725 planning applications from Tower Hamlets, available as JSON over REST or through the MCP server. 6 fields are populated on at least 90% of records.
Measured across all 7,725 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 |
7,725 | 100.0% | |
description |
7,725 | 100.0% | |
reference |
7,725 | 100.0% | |
status |
7,690 | 99.5% | |
status_normalized |
7,690 | 99.5% | |
ward |
7,291 | 94.4% |
| Field | Populated | Coverage | |
|---|---|---|---|
application_type |
6,473 | 83.8% | |
case_officer |
6,468 | 83.7% | |
officer_id |
6,468 | 83.7% | |
applicant_name |
6,439 | 83.4% | |
decision_level |
6,424 | 83.2% | |
decision |
6,060 | 78.4% | |
decision_date |
6,052 | 78.3% | |
postcode |
6,043 | 78.2% | |
decision_normalized |
6,009 | 77.8% | |
standard_type |
5,462 | 70.7% | |
agent_id |
5,199 | 67.3% | |
agent_name |
5,199 | 67.3% | |
agent_company |
4,960 | 64.2% |
| Field | Populated | Coverage | |
|---|---|---|---|
appeal_decision |
145 | 1.9% | |
appeal_decision_normalized |
141 | 1.8% | |
agent_email |
58 | 0.8% | |
property_id |
40 | 0.5% | |
agent_phone |
0 | 0.0% | |
alternative_reference |
0 | 0.0% | |
development_type |
0 | 0.0% | |
easting |
0 | 0.0% | |
northing |
0 | 0.0% | |
officer_recommendation |
0 | 0.0% | |
received_date |
0 | 0.0% |
curl -H "X-Api-Key: $KEY" \ "https://ukplanningapi.co.uk/v1/applications?council_id=120&limit=5"
Council id for Tower Hamlets is 120.
Full endpoint reference →
500 requests a month, free. No card, no password.