Greater Manchester
3,751 planning applications from Tameside, available as JSON over REST or through the MCP server. 16 fields are populated on at least 90% of records.
Measured across all 3,751 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 |
3,751 | 100.0% | |
description |
3,751 | 100.0% | |
received_date |
3,751 | 100.0% | |
reference |
3,751 | 100.0% | |
application_type |
3,748 | 99.9% | |
case_officer |
3,741 | 99.7% | |
officer_id |
3,741 | 99.7% | |
status |
3,741 | 99.7% | |
status_normalized |
3,741 | 99.7% | |
ward |
3,732 | 99.5% | |
applicant_name |
3,728 | 99.4% | |
alternative_reference |
3,536 | 94.3% | |
postcode |
3,503 | 93.4% | |
decision |
3,482 | 92.8% | |
decision_date |
3,482 | 92.8% | |
decision_normalized |
3,475 | 92.6% |
| Field | Populated | Coverage | |
|---|---|---|---|
agent_id |
3,156 | 84.1% | |
agent_name |
3,156 | 84.1% | |
agent_email |
3,119 | 83.2% | |
agent_phone |
3,100 | 82.6% | |
decision_level |
3,081 | 82.1% | |
standard_type |
3,026 | 80.7% | |
agent_company |
2,817 | 75.1% | |
property_id |
703 | 18.7% |
| Field | Populated | Coverage | |
|---|---|---|---|
appeal_decision |
92 | 2.5% | |
appeal_decision_normalized |
92 | 2.5% | |
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=8&limit=5"
Council id for Tameside is 8.
Full endpoint reference →
500 requests a month, free. No card, no password.