Our Unified APIOur unified API brings together data across all modes of transport into a single RESTful API. This API provides access to the most highly requested realtime and status infomation across all the modes of transport, in a single and consistent way. Access to the devloper documentation is available at https://api.tfl.gov.uk
|API area||Example calls||Description|
|Journey planning - Westminster to Bank (Disambiguation)|
Journey planner supports many parameters to help find the right journey given a large number of options relating to mode of transport and accessibility preferences, date/time of travel. These examples use the default preferences. In the first example the results returned offer a selection of options for start and end stations as the inputs "bank" and "westminster" are not precise enough given the number possible locations that include the words Westminster and Bank.
|Journey planning - Westminster to Bank (Results)||https://api.tfl.gov.uk/journey/journeyresults/1000266/to/1000013||This example is showing the results of Westminster underground station to Bank underground station, the inputs are the identifiers of those stations. 3 possible journeys are returned which include all legs of the journey, the stations that the journey goes through, any reported disruptions along the route, the duration of each leg, the instructions for the customer, departure and arrival time for each leg, the mode of transport, the geographical route as a line string of lat/lons, and more.|
|Journey planning - Lat/Lon to postcode (Results)|
|Specifying the start or end of a journey using a lattitude/longitudeor post codes is also supported, in any combination.|
The following examples are for "now", the API also supports dates in the future, where known planned works are factored in to provide a future status.
Returns the current status of the tube lines - Includes status e.g "Good Service" and descriptive text.
|https://api.tfl.gov.uk/line/mode/tube,overground,dlr,tflrail/status||Returns the current status of the tube, overground, dlr, and tflrail in one call.|
|https://api.tfl.gov.uk/line/mode/bus/status||Returns the current status of london buses|
|https://api.tfl.gov.uk/line/mode/national-rail/status||Returns the current status of national-rail services.|
|Detailed information of disruptions to a given station.|
|List all Stops on the 24 Bus route. Each stop Includes: stop name, letter and all lines/routes serving that stop. Facilities at the stop, including toilets, wifi, phone number etc when appropriate, latitude and longitude.|
|https://api.tfl.gov.uk/line/bakerloo/stoppoints||Exact same format of call works for all modes, this example is for the bakerloo line.|
|https://api.tfl.gov.uk/StopPoint/490005183E||Information for a single stop|
|Arrival predictions (countdown/trackernet) for a stop||https://api.tfl.gov.uk/StopPoint/490005183E/arrivals||Returns the real time predicted arrival time of services to a given Stop. Please note arrivals information is also available via a push paradigm using Websockets.|
|Arrival predictions for a route/line.|
|Returns the real time predicated arrival time for all the stops on the given route/line.|
|Line structure (branches)||Returns the names of origin and destinations of routes on a line. E.g. "Harrow & Wealdstone Underground Station" to "Elephant & Castle Underground station"|
|Line structure (branches and stop sequences)||Provides the branches and sequences of stops on the given route and direction. This also includes a Lin string of Lat/Lon showing the path of the route for plotting on maps. Each stop given includes the intercganges with other lines and modes available at each stop.|
|Provides the timetables for the specific route/line at a given stop. This includes the timetable plus the stop sequences|
|Fares (tube only)||Provides fare information for a journey between two stops (tube only)|
|Roads||List TfL Road corridors with their current status.|
|Road disruptions||https://api.tfl.gov.uk/road/a1/disruption||Get the list of current disruption for the given road corridor. This includes the polygon of the disrupted area, along with a textural description and severity assessment. Future disruption information is also available through the API, this includes planned roadworks and road modernisation plans.|
List all Santander Cycle hire docking stations, including 5 minute real-time bike and docking station status information.
Our data downloads
All the data feeds below are available for download. Using our data is subject to our terms and conditions. For a full description of each data feed, along with schema and sample data, please see our feeds page on the TfL website.
Journey Planner API Beta
This API allows you to make requests to TfL's Journey Planner and receive responses as XML. The JP API is IP locked. When we’ve reviewed your registration information we’ll send you an email to let you know if access is granted to the IP address you have provided.
Journey Planner timetables
The Journey Planner timetable feed contains up to date standard timetables for London Underground, bus, DLR and river services.
Our station location feed is a geo-coded KML feed of most London Underground, DLR and London Overground stations.
Our station facilities feed is a Geo-coded KML feed of most London Underground, DLR and London Overground stations. It has station facilities and access information for each station.
Tube departure boards, line status and station status
This feed provides access to real-time Tube data, including a summary train prediction service, a detailed train prediction service, station and line status
Tube - this weekend
Tube - this weekend v2
The 'Tube this weekend' feed contains information on planned line and station closures for the coming weekend. It also has details of planned works affecting station access - such as those involving lifts and escalators.
Bus, Coach and River
Live bus and river bus arrivals API (instant)
This API provides real-time bus and river bus arrival information across all TfL bus stops and piers. Instant requests are responded to with the live bus and river bus arrival information valid at that point in time.
This API provides real-time bus and river bus arrival information across all TfL bus stops and piers. Stream requests are responded to with a continuous supply of live bus and river bus arrival information. Access to the streamed API is password restricted. Once your details have been verified a username and password will be issued by email.
Bus stop locations
This dataset contains information about the location and identifiers for each bus stop served by the London bus network.
This dataset describes the London Buses standard network information. The network information includes the location of all bus stops in London and the sequence of bus stops that every bus route in London stops at.
Bus stop localities
This dataset contains additional location information (road name, locality and borough) for each bus stop served by the London bus network. The locality information contained within is based on a range of sources from the GLA – the locality data is not a definitive record of London’s socio-geographical structure but an aid to help understand London’s localities at a glance.
Coach parking sites/locations
London has a number of coach parking sites that are provided to enable operators to safely park vehicles in areas that will not impede other road users. The file provides geo-coded locations of all coach parking sites along with details such as hours of operation and charging information.
Our pier location feed is a geo-coded KML feed of the piers and docks along the River Thames
Live Traffic Disruptions - TIMS
This feed was built to replace the Live Traffic Disruptions (LTIS) feed, which was decommissioned on 1 April 2013. The new feed has been changed to capture a richer range of information about road disruptions, including improved spatial information, details of closures and more in-depth categorisation of the cause of a disruption.
The Roads disruption API includes additional data on road disruptions (events and planned works) up to 12 months ahead. However, the additional data does not include polygons and affected roads. The location in the additional data may not include borough and postcode information.
Live Roadside Message Signs v2
The live roadside message signs XML feed comes direct from TfL's traffic control centre system and contains the location and live message on every sign currently displaying information in London.
Licensed private hire operators - Findaride
The findaride KML feed contains details of licensed London minicab and other private hire operators. It is based on the same database as the award-winning Cabwise service.
Santander Cycles availability
The Santander Cycles XML feed contains the name, location, coordinates and maximum number of docking points for all operational Santander Cycles docking stations. It also contains the number of available bikes (excluding locked or faulty bikes), and number of available docking points.
Oyster Ticket Stop locations
Our Oyster Ticket Stop locations is a geo-coded KML feed of the 3,700 outlets across London where customers can top up their Oyster card and renew a Travelcard or Bus & Tram Pass.
Step-Free Tube Guide Data - LRAD
The data contained in this feed provides information about the level of step-free access to platforms and trains that is available at London Underground, London Overground and DLR stations.
Information about the PTAL measure and the way it should be used is available from the Planning with WebCAT page. Download the 'Transport connectivity assessment guide' on that page for additional background, examples and other useful measures of connectivity to complement the work with PTAL.
PTAL values are provided for a grid of points at 100 meter intervals, covering the whole of London. The concept of presenting PTAL values for grid points is explained in detail in the guide on the Planning with WebCAT page. The available PTAL data is provided in three files, one for a recent base year and two others for future scenarios in 2021 and 2031.
Each of the files is in CSV format, containing the following data fields:
- A unique identifier for each grid point
- The X (Easting) coordinate, based on the British National Grid
- The Y (Northing) coordinate, based on the British National Grid
- The Access Index (AI) for the point (a calculated value from which we derive PTAL)
- The Public Transport Access Level (PTAL)
The data can be imported into any standard GIS package using the X and Y coordinates.
Rolling Origin & Destination Survey (RODS)
The Rolling O&D survey is an ongoing programme to capture information about journeys on the Tube network.
London Underground passenger counts data
Passenger counts collects information about passenger numbers entering and exiting London Underground stations, largely based on the Underground ticketing system gate data.
This quarterly report details usage, by London borough, for the specified quarter, as well as the same quarter of the previous year to allow for comparison.
Cycle Hire usage data 2012 - 2017
Cycle Hire statistics
Oyster card data
Oyster card journey information
This dataset provides a 5% sample of all Oyster card journeys performed in a week during November 2009 on bus, Tube, DLR and London Overground.