West Midlands
2,050 planning applications from Walsall. Ask questions about them in plain English from ChatGPT or Claude — no coding, about two minutes to set up — or pull them straight into your own software. 9 pieces of information are filled in on at least 90% of records.
Walsall has approved 79.5% of the 1,624 applications it has decided since January 2023. Across the 225 councils with a comparable caseload the range is 71.37% to 99.14%, so this is below the middle of the pack (89.18%).
Decision times can't be measured here — Walsall doesn't publish both a received and a decision date on enough records. The nationwide range across councils that do is 31 to 299 days.
The mix of application types Walsall handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Other | 783 | 38.2% |
| Householder | 567 | 27.7% |
| Full | 422 | 20.6% |
| Tree | 114 | 5.6% |
| Amendment | 63 | 3.1% |
How approval rates and decision times vary across the country →
A "field" is one piece of information on an application — the decision date, the applicant's name, the address. Councils fill these in inconsistently, so this table measures how often Walsall actually provides each one, across all 2,050 records. Anything listed as reliable you can count on; anything lower, check the council's own record before relying on it.
Once this data is connected to ChatGPT or Claude you can just ask "what information does Walsall actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
2,050 | 100.0% | |
Case officercase_officer |
2,050 | 100.0% | |
Description of the worksdescription |
2,050 | 100.0% | |
Council referencereference |
2,050 | 100.0% | |
Wardward |
2,044 | 99.7% | |
Statusstatus |
2,007 | 97.9% | |
Status (standardised wording)status_normalized |
2,007 | 97.9% | |
Applicant's nameapplicant_name |
1,984 | 96.8% | |
Postcodepostcode |
1,982 | 96.7% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Decision datedecision_date |
1,764 | 86.0% | |
Decisiondecision |
1,761 | 85.9% | |
Decision (standardised wording)decision_normalized |
1,724 | 84.1% | |
Agent's nameagent_name |
1,723 | 84.0% | |
Application typeapplication_type |
1,376 | 67.1% | |
Agent's companyagent_company |
1,113 | 54.3% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Appeal decision (standardised wording)appeal_decision_normalized |
0 | 0.0% | |
Date receivedreceived_date |
0 | 0.0% | |
Standardised typestandard_type |
0 | 0.0% |
Walsall's portal has been verified not to publish these fields at all — different from a field that exists but is rarely filled in.
Agent's email Agent's phone Alternative reference Appeal decision Who decided it (officer or committee) Type of development Map coordinates (easting) Map coordinates (northing) Officer's recommendation
Connect it once with your email address, then ask questions like "which extensions were refused in Walsall last year?" or "what's the planning history of this address?" — no coding, about two minutes to set up. Setup guide →
curl -H "X-Api-Key: pk_..." \ "https://ukplanningapi.co.uk/v1/applications?council_id=82&limit=5"
Council id for Walsall is 82.
Full API reference for developers →
500 lookups a month, free. No card, no password — we email you a sign-in link and you're in.