Inner London

City of London planning data

5,390 planning applications from City of London. 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. 13 pieces of information are filled in on at least 90% of records.

5,390

Applications

—

Enforcement notices

512

Appeals

2000–2026

Date range

What City of London decides

City of London has approved 99.14% of the 4,518 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 at or above the middle of the pack (89.18%).

99.14%

Approved, of 4,518 decided

Median days to a decision

135

Average days

What it mostly decides

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

Application type	Applications	Share
Other	2,926	54.3%
Full	1,020	18.9%
Listed building	674	12.5%
Advertisement	380	7.1%
Amendment	285	5.3%

How approval rates and decision times vary across the country →

What City of London 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 City of London actually provides each one, across all 5,390 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 City of London actually fill in?" and get these same numbers back. How to connect →

Reliable — 90% or more of records

Information	Records with it	Coverage
Address `address`	5,390	100.0%
Applicant's name `applicant_name`	5,390	100.0%
Application type `application_type`	5,390	100.0%
Case officer `case_officer`	5,390	100.0%
Description of the works `description`	5,390	100.0%
Date received `received_date`	5,390	100.0%
Council reference `reference`	5,390	100.0%
Ward `ward`	5,390	100.0%
Who decided it (officer or committee) `decision_level`	5,386	99.9%
Agent's email `agent_email`	5,354	99.3%
Status `status`	5,261	97.6%
Status (standardised wording) `status_normalized`	5,261	97.6%
Postcode `postcode`	5,039	93.5%

Partial — use with care

Information	Records with it	Coverage
Alternative reference `alternative_reference`	4,833	89.7%
Decision `decision`	4,813	89.3%
Decision date `decision_date`	4,813	89.3%
Decision (standardised wording) `decision_normalized`	4,785	88.8%
Agent's name `agent_name`	4,543	84.3%
Agent's phone `agent_phone`	4,460	82.7%
Agent's company `agent_company`	4,112	76.3%
Standardised type `standard_type`	3,588	66.6%

Rarely or never published

Information	Records with it	Coverage
Appeal decision `appeal_decision`	26	0.5%
Appeal decision (standardised wording) `appeal_decision_normalized`	26	0.5%
Type of development `development_type`	0	0.0%
Officer's recommendation `officer_recommendation`	0	0.0%

Not published by this council

City of London'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)

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 City of London 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=113&limit=5"

Council id for City of London is 113. Full API reference for developers →

Get free access to City of London data

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