West Midlands
2,247 planning applications from Wolverhampton, available as JSON over REST or through the MCP server. 8 fields are populated on at least 90% of records.
Measured across all 2,247 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 |
2,247 | 100.0% | |
description |
2,247 | 100.0% | |
reference |
2,247 | 100.0% | |
status |
2,247 | 100.0% | |
received_date |
2,240 | 99.7% | |
status_normalized |
2,241 | 99.7% | |
postcode |
2,068 | 92.0% | |
ward |
2,068 | 92.0% |
| Field | Populated | Coverage | |
|---|---|---|---|
alternative_reference |
460 | 20.5% | |
appeal_decision |
460 | 20.5% | |
applicant_name |
460 | 20.5% | |
application_type |
460 | 20.5% | |
case_officer |
461 | 20.5% | |
decision_level |
461 | 20.5% | |
officer_id |
461 | 20.5% | |
agent_id |
384 | 17.1% | |
agent_name |
384 | 17.1% | |
agent_company |
383 | 17.0% | |
decision_normalized |
359 | 16.0% | |
decision_date |
327 | 14.6% | |
decision |
308 | 13.7% | |
agent_email |
277 | 12.3% | |
agent_phone |
262 | 11.7% | |
standard_type |
238 | 10.6% |
| Field | Populated | Coverage | |
|---|---|---|---|
property_id |
21 | 0.9% | |
appeal_decision_normalized |
7 | 0.3% | |
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=83&limit=5"
Council id for Wolverhampton is 83.
Full endpoint reference →
500 requests a month, free. No card, no password.