Month: February 2017

News

TfL Journey Planner Updates – 28 February

Welcome to the latest instalment from the Journey Planner team, designed to keep you up to date with new timetables, stops and points of interest which have been added to the system and timetable data sources over the past week. The Unified API is updated with new Journey Planner data up to five times a week.

Route 215 will serve Lee Valley Camp Site from Saturday 4 March, but the planned diversion of Route W11 from the same date is postponed.

Route 215 will serve Lee Valley Camp Site from Saturday 4 March, but the planned diversion of Route W11 from the same date is postponed.

Read More

Journey Planner

TfL Journey Planner Updates – 21 February

Welcome to the latest instalment from the Journey Planner team, designed to keep you up to date with new timetables, stops and points of interest which have been added to the system and timetable data sources over the past week. The Unified API is updated with new Journey Planner data up to five times a week.

Step-free access is now available at Tottenham Court Road to Central line platforms and Northern line trains and at Canonbury to trains.

Step-free access is now available at Tottenham Court Road to Central line platforms and Northern line trains and at Canonbury to trains.

Read More

Journey Planner

TfL Journey Planner Updates – 14 February

Welcome to the latest instalment from the Journey Planner team, designed to keep you up to date with new timetables, stops and points of interest which have been added to the system and timetable data sources over the past week. The Unified API is updated with new Journey Planner data up to five times a week.

This week's update features a number of changes to stops.

This week’s update includes details of London bus service changes and special services.

Read More

DevelopersInformation

Change to Absolute URLs in API Responses

On Monday 13th February, we will make a minor change to our Unified API responses so that they will no longer return absolute URLs as references to other API entities. They will now return a relative URL instead.

We don’t anticipate many developers are relying on these URLs being absolute, but if we’re wrong, please let us know as soon as possible in the comments section below or through the API portal.

url-code-screenshot-2

Next Monday we’re making a minor change to our Unified API responses, so that they will no longer return absolute URLs as references to other API entities

Read More