We’re holding a consultation into our Transparency Strategy, and we’d love to hear from you about how we can improve.
The Strategy covers our open data products, so we want to hear from the developer community about our Unified API and open data. We want to know how we can improve our products to give you regular, up to date and useful information, as well as the formats in which this data should be published.
We’re also keen to hear how you think this data should be grouped or presented on the TfL website, and whether we need to give further support to developers, stakeholders and researchers who use it.
The consultation is running for six weeks, from 18 September to 29 October.
While we always encourage comments to these blog posts, to make sure your voice is heard visit our Consultation website to have your say.
It’s great to see so many customer-facing apps using TfL’s open data. With over 600 apps in areas of public transport, active travel and healthier streets, we are continually focused on releasing new data.
There are lots of people involved in the ecosystem, ranging from app developers and start-ups to accelerator programmes.
We are excited to launch our new TfL Oyster app on iOS and Android, which allows customers to top up their Oyster cards, purchase Travelcards and view their journey history. The app was launched last week, and has already received lots of great feedback. We wanted to offer you more insight into how we developed it.
The TfL Oyster app launched last week – let us know what you think in the comments section below.
An API – or application programming interface – is a set of subroutine definitions, protocols and tools for building application software¹. We already have a wide range of public APIs, which provide information such as line status, bus status and journey information. To build a mobile application allowing customers access to their Oyster card data through, we needed to write a new API to support this.