Essex
3,379 planning applications from Uttlesford, available as JSON over REST or through the MCP server. 3 fields are populated on at least 90% of records.
Measured across all 3,379 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,379 | 100.0% | |
description |
3,379 | 100.0% | |
reference |
3,379 | 100.0% |
| Field | Populated | Coverage | |
|---|---|---|---|
postcode |
2,538 | 75.1% | |
ward |
2,044 | 60.5% |
| Field | Populated | Coverage | |
|---|---|---|---|
alternative_reference |
224 | 6.6% | |
appeal_decision |
224 | 6.6% | |
applicant_name |
224 | 6.6% | |
application_type |
224 | 6.6% | |
case_officer |
224 | 6.6% | |
decision_level |
224 | 6.6% | |
officer_id |
224 | 6.6% | |
received_date |
224 | 6.6% | |
standard_type |
203 | 6.0% | |
agent_company |
171 | 5.1% | |
agent_id |
171 | 5.1% | |
agent_name |
171 | 5.1% | |
decision_date |
163 | 4.8% | |
status |
146 | 4.3% | |
status_normalized |
142 | 4.2% | |
decision |
119 | 3.5% | |
decision_normalized |
118 | 3.5% | |
agent_email |
27 | 0.8% | |
agent_phone |
21 | 0.6% | |
appeal_decision_normalized |
7 | 0.2% | |
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=451&limit=5"
Council id for Uttlesford is 451.
Full endpoint reference →
500 requests a month, free. No card, no password.