West Yorkshire
2,250 planning applications from Kirklees, available as JSON over REST or through the MCP server. 12 fields are populated on at least 90% of records.
Measured across all 2,250 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 | |
|---|---|---|---|
reference |
2,250 | 100.0% | |
address |
2,245 | 99.8% | |
description |
2,245 | 99.8% | |
received_date |
2,245 | 99.8% | |
ward |
2,245 | 99.8% | |
applicant_name |
2,244 | 99.7% | |
case_officer |
2,244 | 99.7% | |
officer_id |
2,244 | 99.7% | |
alternative_reference |
2,233 | 99.2% | |
postcode |
2,182 | 97.0% | |
decision |
2,146 | 95.4% | |
status |
2,146 | 95.4% |
| Field | Populated | Coverage | |
|---|---|---|---|
decision_date |
1,988 | 88.4% | |
status_normalized |
1,830 | 81.3% | |
decision_normalized |
1,828 | 81.2% | |
agent_id |
1,673 | 74.4% | |
agent_name |
1,673 | 74.4% |
| Field | Populated | Coverage | |
|---|---|---|---|
appeal_decision |
27 | 1.2% | |
appeal_decision_normalized |
27 | 1.2% | |
agent_company |
0 | 0.0% | |
agent_email |
0 | 0.0% | |
agent_phone |
0 | 0.0% | |
application_type |
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% | |
property_id |
0 | 0.0% | |
standard_type |
0 | 0.0% |
curl -H "X-Api-Key: $KEY" \ "https://ukplanningapi.co.uk/v1/applications?council_id=41&limit=5"
Council id for Kirklees is 41.
Full endpoint reference →
500 requests a month, free. No card, no password.