Transport for London Unified API OpenAPI specification.
84 operations in the validated baseline. Release comparisons appear after another revision is captured. Baseline verified 2026-11-11 UTC.
Transport for London Unified API public API specification, version v1.
0 recorded releases · Last captured 11 Nov 2026.
What does the Transport for London Unified API specification cover?
This public contract baseline contains 84 API operations. Version v1 passed parsing, reference resolution and normalization on . A baseline establishes a revision to compare; it does not establish that an API has no breaking changes.
| Operation | Summary |
|---|---|
GET /AccidentStats/{year} | Gets all accident details for accidents occuring in the specified year |
GET /AirQuality | Gets air quality data feed |
GET /BikePoint | Gets all bike point locations. The Place object has an addtionalProperties array which contains the nbBikes, nbDocks and nbSpaces numbers which give the status of the BikePoint. A mismatch in these numbers i.e. nbDocks - (nbBikes + nbSpaces) != 0 indicates broken docks. |
GET /BikePoint/Search | Search for bike stations by their name, a bike point's name often contains information about the name of the street or nearby landmarks, for example. Note that the search result does not contain the PlaceProperties i.e. the status or occupancy of the BikePoint, to get that information you should retrieve the BikePoint by its id on /BikePoint/id. |
Source and revision provenance
- Directory contract
- APIs.guru: tfl.gov.uk
- Upstream source listed by the directory
- View the listed upstream specification
- Directory revision updated
- Normalized SHA-256
3cfe3df81a5a44f2d71b5c15292e131ba770ba47313faf5ed9172b22cf0284c8- Source SHA-256
8ec97a3a03307f0849135f0b69096598fd32a82770ef8cdf10992ab53c57b0b4- Reported source license
- Not declared in directory metadata
This is a version-pinned directory snapshot. The validation date is not a publisher release date. Scheduled source polling is not enabled for this baseline. SDK matching and repair coverage depend on the configured integration.
Explore public API evidence with MCP · Check repository coverage in GitHub