Northumberland
300 planning applications from Northumberland (Park), available as JSON over REST or through the MCP server. 15 fields are populated on at least 90% of records.
We hold only 300 applications here. Treat an absent record as "not published to us", never as "no such application".
Measured across all 300 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 |
300 | 100.0% | |
address |
299 | 99.7% | |
decision |
299 | 99.7% | |
description |
299 | 99.7% | |
received_date |
299 | 99.7% | |
status |
299 | 99.7% | |
applicant_name |
297 | 99.0% | |
status_normalized |
297 | 99.0% | |
easting |
296 | 98.7% | |
northing |
296 | 98.7% | |
agent_id |
292 | 97.3% | |
agent_name |
292 | 97.3% | |
decision_date |
283 | 94.3% | |
postcode |
276 | 92.0% | |
ward |
275 | 91.7% |
| Field | Populated | Coverage | |
|---|---|---|---|
decision_normalized |
266 | 88.7% | |
agent_company |
38 | 12.7% | |
agent_email |
35 | 11.7% |
| Field | Populated | Coverage | |
|---|---|---|---|
agent_phone |
0 | 0.0% | |
alternative_reference |
0 | 0.0% | |
appeal_decision |
0 | 0.0% | |
appeal_decision_normalized |
0 | 0.0% | |
application_type |
0 | 0.0% | |
case_officer |
0 | 0.0% | |
decision_level |
0 | 0.0% | |
development_type |
0 | 0.0% | |
officer_id |
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=356&limit=5"
Council id for Northumberland (Park) is 356.
Full endpoint reference →
500 requests a month, free. No card, no password.