Lothian
21,640 planning applications from Edinburgh. 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. 12 pieces of information are filled in on at least 90% of records.
We don't yet have Edinburgh'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.
Edinburgh has approved 81.84% of the 15,064 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%).
The mix of application types Edinburgh handles — useful for telling whether your kind of application is routine here or unusual.
| Application type | Applications | Share |
|---|---|---|
| Other | 10,724 | 49.6% |
| Listed building | 4,372 | 20.2% |
| Tree | 3,063 | 14.2% |
| Certificate | 2,649 | 12.2% |
| Amendment | 830 | 3.8% |
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 Edinburgh actually provides each one, across all 21,640 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 Edinburgh actually fill in?" and get these same numbers back. How to connect →
| Information | Records with it | Coverage | |
|---|---|---|---|
Addressaddress |
21,639 | 100.0% | |
Description of the worksdescription |
21,640 | 100.0% | |
Council referencereference |
21,640 | 100.0% | |
Statusstatus |
21,401 | 98.9% | |
Wardward |
21,374 | 98.8% | |
Application typeapplication_type |
21,359 | 98.7% | |
Applicant's nameapplicant_name |
21,335 | 98.6% | |
Who decided it (officer or committee)decision_level |
21,347 | 98.6% | |
Case officercase_officer |
20,623 | 95.3% | |
Decisiondecision |
19,966 | 92.3% | |
Decision datedecision_date |
19,967 | 92.3% | |
Postcodepostcode |
19,499 | 90.1% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Status (standardised wording)status_normalized |
18,842 | 87.1% | |
Agent's nameagent_name |
18,050 | 83.4% | |
Agent's phoneagent_phone |
17,293 | 79.9% | |
Agent's emailagent_email |
17,274 | 79.8% | |
Decision (standardised wording)decision_normalized |
16,563 | 76.5% | |
Appeal decisionappeal_decision |
2,773 | 12.8% |
| Information | Records with it | Coverage | |
|---|---|---|---|
Standardised typestandard_type |
1,931 | 8.9% | |
Agent's companyagent_company |
1,687 | 7.8% | |
Appeal decision (standardised wording)appeal_decision_normalized |
861 | 4.0% | |
Date receivedreceived_date |
303 | 1.4% | |
Alternative referencealternative_reference |
1 | 0.0% | |
Type of developmentdevelopment_type |
0 | 0.0% | |
Officer's recommendationofficer_recommendation |
0 | 0.0% |
Edinburgh'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 Edinburgh 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=146&limit=5"
Council id for Edinburgh is 146.
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.