← All councils

West Midlands

Birmingham planning data

23,346 planning applications from Birmingham. 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. 14 pieces of information are filled in on at least 90% of records.

23,346
Applications
—
Enforcement notices
1,511
Appeals
2023–2026
Date range

What Birmingham decides

Birmingham has approved 83.21% of the 20,020 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%).

83.21%
Approved, of 20,020 decided
62.5
Median days to a decision
90.3
Average days

What it mostly decides

The mix of application types Birmingham handles — useful for telling whether your kind of application is routine here or unusual.

Application typeApplications Share
Householder 10,810 46.3%
Full 4,051 17.4%
Conditions 2,886 12.4%
Other 1,658 7.1%
Certificate 1,537 6.6%

How approval rates and decision times vary across the country →

What Birmingham actually fills in

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 Birmingham actually provides each one, across all 23,346 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 Birmingham actually fill in?" and get these same numbers back. How to connect →

Reliable — 90% or more of records

InformationRecords with it Coverage
Address
address
23,346 100.0%
Application type
application_type
23,346 100.0%
Description of the works
description
23,342 100.0%
Date received
received_date
23,343 100.0%
Council reference
reference
23,346 100.0%
Status
status
23,346 100.0%
Status (standardised wording)
status_normalized
23,346 100.0%
Applicant's name
applicant_name
23,139 99.1%
Ward
ward
23,129 99.1%
Case officer
case_officer
23,104 99.0%
Postcode
postcode
22,625 96.9%
Decision
decision
21,932 93.9%
Decision date
decision_date
21,898 93.8%
Decision (standardised wording)
decision_normalized
21,079 90.3%

Partial — use with care

InformationRecords with it Coverage
Agent's name
agent_name
20,952 89.7%

Rarely or never published

InformationRecords with it Coverage
Agent's company
agent_company
220 0.9%
Appeal decision (standardised wording)
appeal_decision_normalized
0 0.0%
Map coordinates (easting)
easting
0 0.0%
Map coordinates (northing)
northing
0 0.0%
Standardised type
standard_type
0 0.0%

Not published by this council

Birmingham'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 Officer's recommendation

Get this data

Ask it in ChatGPT or Claude

Connect it once with your email address, then ask questions like "which extensions were refused in Birmingham last year?" or "what's the planning history of this address?" — no coding, about two minutes to set up. Setup guide →

Or call it from your own code

curl -H "X-Api-Key: pk_..." \
  "https://ukplanningapi.co.uk/v1/applications?council_id=81419&limit=5"

Council id for Birmingham is 81419. Full API reference for developers →

Get free access to Birmingham data

500 lookups a month, free. No card, no password — we email you a sign-in link and you're in.