Cheshire
803 planning applications from Chester, available as JSON over REST or through the MCP server. 10 fields are populated on at least 90% of records.
Measured across all 803 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 |
803 | 100.0% | |
description |
803 | 100.0% | |
reference |
803 | 100.0% | |
status |
802 | 99.9% | |
status_normalized |
802 | 99.9% | |
received_date |
793 | 98.8% | |
ward |
792 | 98.6% | |
applicant_name |
750 | 93.4% | |
application_type |
750 | 93.4% | |
standard_type |
750 | 93.4% |
| Field | Populated | Coverage | |
|---|---|---|---|
postcode |
664 | 82.7% | |
alternative_reference |
651 | 81.1% | |
case_officer |
562 | 70.0% | |
officer_id |
562 | 70.0% | |
agent_email |
530 | 66.0% | |
agent_id |
530 | 66.0% | |
agent_name |
530 | 66.0% | |
decision_date |
447 | 55.7% | |
decision |
424 | 52.8% | |
decision_normalized |
405 | 50.4% | |
agent_company |
296 | 36.9% | |
property_id |
81 | 10.1% |
| Field | Populated | Coverage | |
|---|---|---|---|
appeal_decision |
7 | 0.9% | |
appeal_decision_normalized |
7 | 0.9% | |
agent_phone |
0 | 0.0% | |
decision_level |
0 | 0.0% | |
development_type |
0 | 0.0% | |
easting |
0 | 0.0% | |
northing |
0 | 0.0% | |
officer_recommendation |
0 | 0.0% |
curl -H "X-Api-Key: $KEY" \ "https://ukplanningapi.co.uk/v1/applications?council_id=202&limit=5"
Council id for Chester is 202.
Full endpoint reference →
500 requests a month, free. No card, no password.