Our Unified API
Example Unified API calls
Access to the developer documentation is available at https://api.tfl.gov.uk
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 open data page on the TfL website.
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.
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.
This feed provides access to real-time Tube data, including a summary train prediction service, a detailed train prediction service, station and line status
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
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.
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.
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.
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
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.
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.
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.
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.
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.
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.
The Rolling O&D survey is an ongoing programme to capture information about journeys on the Tube network.
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
Oyster card data
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.
Please email email@example.com for assistance