Pricing overview

Transport for London (TfL) provides its API access primarily free of charge for developers, researchers, and organizations that utilize London's public transport data. The model is designed to encourage innovation and the development of applications that benefit commuters and visitors to London. Users must register for an API account to obtain credentials, which grant access to various data feeds including real-time line statuses, journey planning endpoints, and disruption information TfL API account creation. This free access covers typical usage scenarios for most application development and data analysis needs.

For operations requiring significantly higher request volumes or specialized data access beyond the standard API offerings, TfL indicates that users may need to contact them directly to discuss potential custom access arrangements. However, the foundational API services remain accessible without direct monetary cost for registered users. This approach supports a broad ecosystem of third-party applications and services built upon TfL data.

Plans and tiers

TfL's API access operates with a straightforward, two-tiered model: a standard free tier and a custom arrangement for high-volume or specialized use cases. Unlike commercial API providers that often feature multiple subscription tiers with varying request limits and feature sets, TfL's structure is less about monetizing access and more about managing resource allocation for its public service data.

Plan Price Key Limits Best For
Standard Free Access £0.00 Subject to fair usage policies (undisclosed, but typical for application development)

  • Individual developers
  • Small to medium-sized applications
  • Real-time journey planning apps
  • Academic research projects
  • Public transport data analysis
Custom / High Volume Access Contact TfL for pricing Negotiated based on specific requirements
  • Enterprise-level applications
  • Services requiring extremely high request rates
  • Specialized data sets or bespoke integrations
  • Large-scale urban planning tools

The standard free access tier is suitable for the majority of developers looking to integrate London transport information into their applications, websites, or data analysis projects. Details regarding specific request per minute (RPM) or daily request limits for the standard free tier are not explicitly published, indicating a flexible "fair usage" policy. Developers are encouraged to design their applications efficiently to minimize unnecessary API calls. For clarity on what constitutes high-volume usage, direct consultation with TfL is recommended.

Free tier and limits

The core of TfL's API offering is its free tier, available to anyone who registers for an API account. This includes access to a wide range of data, from live tube and bus statuses to planned disruptions and journey planning functionality TfL API reference. The free tier aims to support a vibrant developer community and foster innovation around London's transport network.

While specific hard limits for the free tier are not publicly detailed, it operates under a general "fair usage" policy. This policy is common among public service APIs and implies that usage should be reasonable and not impose an undue burden on the API infrastructure. For example, developers are typically expected to:

  • Cache data where appropriate, rather than making repeated identical requests.
  • Implement exponential backoff for retrying failed requests to avoid overwhelming the service during temporary outages.
  • Only request data necessary for their application's function.

Exceeding perceived fair usage may result in rate limiting or, in extreme cases, temporary suspension of API access. Developers can monitor their usage patterns and application performance to ensure compliance with these implied guidelines. The absence of explicit numerical limits provides flexibility but also places responsibility on developers to act as good API citizens. Should an application's needs grow to a scale that might challenge these unstated limits, contacting TfL for guidance on custom access is the appropriate next step.

Real-world cost examples

Given TfL's free-tier-centric pricing model, real-world cost examples primarily demonstrate scenarios under the free access policy, with a distinction for when custom arrangements might become necessary.

Example 1: Mobile Journey Planner App (Free Tier)

  • Scenario: A startup develops a mobile application that provides real-time journey planning, line status updates, and identifies nearby transport options for users in London. The app has approximately 50,000 active users who collectively make an average of 1 million API calls per day for live data.
  • API Calls: 1 million requests/day (e.g., 500,000 journey plan requests, 300,000 line status requests, 200,000 nearby station lookups).
  • Cost: £0.00. This level of usage, while substantial, typically falls within the expected fair usage of the standard free tier, especially if requests are optimized and cached where possible.
  • Consideration: The startup would need to ensure their application design is efficient in its API calls to remain within the spirit of the fair usage policy.

Example 2: Academic Research Project (Free Tier)

  • Scenario: A university research team analyzing historical public transport delays and passenger flow for a specific period of 6 months. They perform batch requests on historical data (where available or derived) and make periodic real-time calls to gather current line statuses for comparative analysis. The total historical data retrieval takes several weeks, followed by daily real-time monitoring.
  • API Calls: Initial bulk data retrieval (e.g., 200,000 requests over a month) and ongoing real-time data collection (e.g., 5,000 requests/day).
  • Cost: £0.00. Academic projects with defined scopes and reasonable request patterns are well-supported by the free tier.
  • Consideration: Researchers should plan their data retrieval to avoid overwhelming the API with excessively rapid batch requests, especially during peak times.

Example 3: Large-Scale Urban Planning Platform (Potential Custom Arrangement)

  • Scenario: A large urban development company builds an internal platform that integrates live TfL data with other city planning datasets. The platform serves thousands of internal users, runs complex simulations, and requires constant, high-frequency updates across nearly all TfL API endpoints for multiple planning models simultaneously. This generates an estimated 10 million API calls per day, with stringent latency and uptime requirements.
  • API Calls: 10 million+ requests/day.
  • Cost: Contact TfL for custom pricing. This scale of usage, combined with potential requirements for dedicated support or service level agreements, would likely necessitate a formal discussion with TfL to establish a custom access agreement and associated costs.
  • Consideration: Such an entity would engage directly with TfL to ensure their operational needs are met without impacting the broader public service.

How the pricing compares

When comparing TfL's API pricing with alternatives, it is crucial to consider the nature of the data provided and the primary purpose of each service. TfL's API focuses exclusively on London's public transport network, offered largely as a public service.

  • Google Maps Platform: Google Maps Platform offers a comprehensive suite of APIs covering mapping, routing, places, and more, globally Google Maps Platform overview. Its pricing is usage-based, with a free tier that includes a monthly credit, but charges apply for exceeding those limits. For instance, the Geocoding API costs $5.00 per 1000 requests after the initial free usage, and Static Maps can cost $2.00 per 1000 requests Google Maps Platform pricing. While Google Maps Platform offers global coverage and broader functionality, integrating London-specific real-time transport data through it might still require cross-referencing with TfL's API for the most authoritative and up-to-date information, or relying on Google's own data which may not always be as granular for specific local transport networks.
  • Moovit: Moovit provides a global public transport app and also offers an API. While detailed public API pricing for Moovit is not readily available on their website, similar commercial transit data APIs typically operate on subscription models or usage-based pricing determined by factors like user count, geographic scope, and request volume. Moovit's strength lies in its global coverage, but for London, TfL remains the primary and most direct source of real-time operational data.
  • OpenTripPlanner: OpenTripPlanner is an open-source multimodal trip planner. It is free to use and deploy, but the costs come in hosting, maintenance, and data integration (e.g., acquiring and processing GTFS feeds and street network data). While it offers flexibility and ownership over the infrastructure, it requires significant technical expertise and resources to set up and maintain, unlike TfL's hosted API.

In summary, TfL's free-tier approach makes it highly competitive for developers focused solely on London transport data, eliminating direct costs for most use cases. Alternatives like Google Maps Platform offer broader geographical and functional scope but come with usage-based costs. Open-source solutions like OpenTripPlanner provide cost-free software but shift the expenditure to infrastructure and operational overhead.