TfL Open Data & Unified API
This overview was generated with AI from the public sources listed below and checked against them before publication. It has not had a complete human fact-check — treat it as a starting point and follow the sources.
11 sourced claims on this page, none individually verified yet — turn on “Sources in the text” to see each one.
How this atlas is made · What “last verified” means · What “source-checked” means · The full record behind this page
TfL spends about £1m a year publishing its feeds; a Deloitte study it commissioned valued the return at up to £130m a year. The apps 42% of Londoners use were built by somebody else.
what does this mean?
The strongest source is the operator's or the city's own reporting — an official report, dataset or press release. It grades who did the looking — not how well the project went. All four grades →Part of 1001 Smart Cities — 1,216 documented projects · 🏙️ 15 more in London · 📊 Open data guide · 📡 Data & IoT projects
Transport for London publishes its transport data free of charge for anyone to reuse — more than 80 data feeds at the time of the 2017 review, around 75% of them through APIs, now served through its Unified API — covering the Tube, buses, roads and cycle hire. A July 2017 Deloitte study commissioned by TfL valued the open-data policy at up to £130m a year in economic benefits and time savings, with over 13,000 registered developers and more than 600 apps used by 42% of Londoners.
📊 Impact
Deloitte (July 2017) estimated up to £130m/year in economic benefits and savings, against a TfL cost of about £1m/year to publish the data — and roughly 500 direct jobs plus 230 in the supply chain. Self-commissioned figures.
🎓 Lesson
Publishing raw feeds openly, rather than building official apps, let a third-party developer ecosystem deliver journey tools at a fraction of the cost of doing it in-house.
Sources
Show your work What this page rests on and what it can’t tell you · all 11 claims with their sources · the forensic record
Evidence file · public beta 11 addressable claims, 3 source dossiers, one permanent baseline. The file is unreviewed — an AI-assisted structural migration, not a human or expert endorsement. Every revision keeps a permanent copy under revision history.
Inspect the claims, one by one — verbatim text, sources and caveats for all 11
The text below is copied verbatim from the published record. Each claim names the source dossiers that carry it; caveats stay attached to the claim they qualify.
clm-fcc76892569b8022
descriptive
Transport for London publishes its transport data free of charge for anyone to reuse
Sources carrying this claim
clm-5b9e724a4d213086
quantitative
more than 80 data feeds at the time of the 2017 review, around 75% of them through APIs
Sources carrying this claim
clm-ddb6c2778371cb7c
descriptive
now served through its Unified API
Sources carrying this claim
clm-9a31ebe3ac1c8be2
descriptive
covering the Tube, buses, roads and cycle hire
Sources carrying this claim
clm-d3dc130d29de0e65
quantitative
A July 2017 Deloitte study commissioned by TfL
Sources carrying this claim
clm-792312a4f7e283dd
quantitative
valued the open-data policy at up to £130m a year in economic benefits and time savings
Sources carrying this claim
clm-3066af5292e9503a
quantitative
over 13,000 registered developers
Sources carrying this claim
clm-430bc3bdfb12f05f
quantitative
more than 600 apps used by 42% of Londoners
Sources carrying this claim
clm-9518e99211302148
quantitative
against a TfL cost of about £1m/year to publish the data
Sources carrying this claim
clm-d9b3c404200fe4d7
quantitative
roughly 500 direct jobs plus 230 in the supply chain
Sources carrying this claim
clm-5034d1cfe97287d7
descriptive
let a third-party developer ecosystem deliver journey tools at a fraction of the cost of doing it in-house
Sources carrying this claim
Forensic record — source dossiers, gaps, hashes and the exact revision this page renders
This layer records what is known about each source, what is still missing, and the exact snapshot this page is rendering. A missing date, archive or hash stays visible as missing.
Awaiting operator and domain-expert review; publication of this revision implies neither.
sha256:4f60c1b97f651ec229110077f7d9d5871e685ba28065b74adea7b427e5f9e347
- 11
- of 11 claims mapped
- 3
- source dossiers
- 0
- publication dates recorded
- 0
- archives linked
- 0
- exact locators
- 0
- content captures hashed
Governance facts carried by the record
- Operator
- Transport for London (TfL)
- Actor types
- utility
- Funding model
- public
- Funding description
- Not recorded
- Cost
- Not recorded
- Ownership
- Not recorded
- Decision rights
- Not recorded
- Exit conditions
- Not recorded
3 source dossiers
Deloitte / TfL report (authority)
- Stable source ID
src-c1b3d956614ccd38- Publisher
- Name not classified · content.tfl.gov.uk
- Type / language
- pdf · language not classified
- Published
- Not recorded
- Updated
- Not recorded
- Source last checked
- No source-level check date
- Record last verified
- 2026-09-27
- Dossier created
- 2026-09-27
- Retrieved copy
- No local capture recorded
- Archive
- No archived copy linked
- Content hash
- No captured content hash
- Locator
- Descriptive only — not page/paragraph exact
Open the recorded source note
'Assessing the value of TfL's open data and digital partnerships', July 2017 — source of the figures.
UK Government API Catalogue (official)
- Stable source ID
src-b624f44d15bcf25f- Publisher
- Name not classified · api.gov.uk
- Type / language
- web-page · language not classified
- Published
- Not recorded
- Updated
- Not recorded
- Source last checked
- No source-level check date
- Record last verified
- 2026-09-27
- Dossier created
- 2026-09-27
- Retrieved copy
- No local capture recorded
- Archive
- No archived copy linked
- Content hash
- No captured content hash
- Locator
- Descriptive only — not page/paragraph exact
Open the recorded source note
Central-government API catalogue listing of TfL's Unified API, its endpoint and documentation.
- Claims linked
Transport for London — API portal (developer registration)
- Stable source ID
src-88b061df925431ca- Publisher
- Name not classified · api-portal.tfl.gov.uk
- Type / language
- web-page · language not classified
- Published
- Not recorded
- Updated
- Not recorded
- Source last checked
- No source-level check date
- Record last verified
- 2026-09-27
- Dossier created
- 2026-09-27
- Retrieved copy
- No local capture recorded
- Archive
- No archived copy linked
- Content hash
- No captured content hash
- Locator
- Descriptive only — not page/paragraph exact
Open the recorded source note
TfL's developer portal: register for an account, subscribe to the 500-requests data plan and use an app_key; data is released for reuse under TfL's transport data terms and conditions.
- Claims linked
Known limits of this file
- Publisher names and source languages have not yet been classified; domains are recorded without guessing.
- Existing source notes are descriptive locators, not page- or paragraph-exact citations.
- A missing archive, publication date or content hash is shown as null rather than inferred.
- The project-level evidence grade ranks the strongest source in the entry; it is not a truth score for every claim.
Continue exploring
Compare this project
Explore the wider context
📎 Cite this project
1001 Smart Cities (2026). “TfL Open Data & Unified API” — London, United Kingdom. The Smart City Atlas. https://1001smartcities.org/projects/london-tfl-open-data/ (last verified 2026-09-27). Data: CC BY 4.0.
The underlying data is free to reuse with attribution — see the open data page.
