Gloucestershire
2,486 planning applications from Gloucester, available as JSON over REST or through the MCP server. 3 fields are populated on at least 90% of records.
Measured across all 2,486 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,486 | 100.0% | |
description |
2,486 | 100.0% | |
reference |
2,486 | 100.0% |
| Field | Populated | Coverage | |
|---|---|---|---|
ward |
2,059 | 82.8% | |
postcode |
2,043 | 82.2% |
| Field | Populated | Coverage | |
|---|---|---|---|
application_type |
229 | 9.2% | |
received_date |
228 | 9.2% | |
case_officer |
227 | 9.1% | |
officer_id |
227 | 9.1% | |
applicant_name |
217 | 8.7% | |
standard_type |
217 | 8.7% | |
alternative_reference |
185 | 7.4% | |
decision_date |
181 | 7.3% | |
agent_id |
151 | 6.1% | |
agent_name |
151 | 6.1% | |
agent_company |
143 | 5.8% | |
decision |
131 | 5.3% | |
decision_normalized |
123 | 4.9% | |
status |
95 | 3.8% | |
status_normalized |
95 | 3.8% | |
agent_email |
13 | 0.5% | |
agent_phone |
12 | 0.5% | |
property_id |
11 | 0.4% | |
decision_level |
8 | 0.3% | |
appeal_decision |
3 | 0.1% | |
appeal_decision_normalized |
3 | 0.1% | |
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=268&limit=5"
Council id for Gloucester is 268.
Full endpoint reference →
500 requests a month, free. No card, no password.