Lancashire
2,130 planning applications from Burnley, available as JSON over REST or through the MCP server. 12 fields are populated on at least 90% of records.
Measured across all 2,130 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,130 | 100.0% | |
application_type |
2,130 | 100.0% | |
decision_level |
2,130 | 100.0% | |
description |
2,130 | 100.0% | |
reference |
2,130 | 100.0% | |
status |
2,130 | 100.0% | |
ward |
2,130 | 100.0% | |
case_officer |
2,125 | 99.8% | |
officer_id |
2,125 | 99.8% | |
status_normalized |
2,125 | 99.8% | |
applicant_name |
2,071 | 97.2% | |
postcode |
1,976 | 92.8% |
| Field | Populated | Coverage | |
|---|---|---|---|
decision_date |
1,825 | 85.7% | |
decision |
1,759 | 82.6% | |
decision_normalized |
1,500 | 70.4% | |
agent_id |
1,417 | 66.5% | |
agent_name |
1,417 | 66.5% | |
standard_type |
730 | 34.3% |
| Field | Populated | Coverage | |
|---|---|---|---|
agent_company |
0 | 0.0% | |
agent_email |
0 | 0.0% | |
agent_phone |
0 | 0.0% | |
alternative_reference |
0 | 0.0% | |
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% | |
received_date |
0 | 0.0% |
curl -H "X-Api-Key: $KEY" \ "https://ukplanningapi.co.uk/v1/applications?council_id=18&limit=5"
Council id for Burnley is 18.
Full endpoint reference →
500 requests a month, free. No card, no password.