Cheshire
1,733 planning applications from Halton, available as JSON over REST or through the MCP server. 6 fields are populated on at least 90% of records.
Measured across all 1,733 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 |
1,733 | 100.0% | |
description |
1,733 | 100.0% | |
received_date |
1,733 | 100.0% | |
reference |
1,733 | 100.0% | |
status |
1,733 | 100.0% | |
status_normalized |
1,733 | 100.0% |
| Field | Populated | Coverage | |
|---|---|---|---|
postcode |
1,476 | 85.2% | |
ward |
1,473 | 85.0% | |
application_type |
227 | 13.1% | |
applicant_name |
226 | 13.0% | |
alternative_reference |
223 | 12.9% | |
case_officer |
224 | 12.9% | |
officer_id |
224 | 12.9% | |
standard_type |
207 | 11.9% |
| Field | Populated | Coverage | |
|---|---|---|---|
agent_id |
163 | 9.4% | |
agent_name |
163 | 9.4% | |
agent_company |
160 | 9.2% | |
decision_date |
144 | 8.3% | |
decision |
137 | 7.9% | |
decision_normalized |
121 | 7.0% | |
agent_email |
36 | 2.1% | |
agent_phone |
27 | 1.6% | |
decision_level |
12 | 0.7% | |
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=32&limit=5"
Council id for Halton is 32.
Full endpoint reference →
500 requests a month, free. No card, no password.