West Yorkshire
29,880 planning applications from Leeds. 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. 10 pieces of information are filled in on at least 90% of records.
We don't yet have Leeds's full history back to 2023 — it's loading now. The figures below cover what we already hold, so treat them as a minimum rather than the full picture. Alerts for new day-to-day changes start once loading is complete.
Leeds has approved 83.58% of the 20,560 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 — Leeds 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 Leeds handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Full | 12,117 | 40.6% |
| Conditions | 5,225 | 17.5% |
| Tree | 3,852 | 12.9% |
| Other | 3,398 | 11.4% |
| Certificate | 2,947 | 9.9% |
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 Leeds actually provides each one, across all 29,880 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 Leeds actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
29,880 | 100.0% | |
Description of the worksdescription |
29,880 | 100.0% | |
Council referencereference |
29,880 | 100.0% | |
Statusstatus |
29,880 | 100.0% | |
Status (standardised wording)status_normalized |
29,880 | 100.0% | |
Wardward |
29,597 | 99.1% | |
Application typeapplication_type |
27,940 | 93.5% | |
Applicant's nameapplicant_name |
27,909 | 93.4% | |
Who decided it (officer or committee)decision_level |
27,915 | 93.4% | |
Postcodepostcode |
27,612 | 92.4% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Decision datedecision_date |
25,315 | 84.7% | |
Decisiondecision |
25,102 | 84.0% | |
Decision (standardised wording)decision_normalized |
25,084 | 83.9% | |
Agent's nameagent_name |
22,827 | 76.4% | |
Agent's emailagent_email |
20,072 | 67.2% | |
Agent's phoneagent_phone |
20,042 | 67.1% | |
Standardised typestandard_type |
6,498 | 21.7% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Agent's companyagent_company |
872 | 2.9% | |
Appeal decisionappeal_decision |
663 | 2.2% | |
Appeal decision (standardised wording)appeal_decision_normalized |
663 | 2.2% | |
Alternative referencealternative_reference |
0 | 0.0% | |
Case officercase_officer |
0 | 0.0% | |
Type of developmentdevelopment_type |
0 | 0.0% | |
Officer's recommendationofficer_recommendation |
0 | 0.0% | |
Date receivedreceived_date |
0 | 0.0% |
Leeds's portal has been verified not to publish these fields at all — different from a field that exists but is rarely filled in.
Map coordinates (easting) Map coordinates (northing)
Connect it once with your email address, then ask questions like "which extensions were refused in Leeds 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=42&limit=5"
Council id for Leeds is 42.
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.