Pricing overview
Transport for Germany's API pricing is structured around a request-based model designed to accommodate varying usage levels, from individual developers to large enterprises. The core principle involves a tiered subscription approach, where each plan bundles a specific number of API requests per month at a fixed cost. Exceeding plan limits typically incurs overage fees per additional request. This model is common among API providers, balancing predictable costs with scalability (Google Maps Platform pricing documentation).
The pricing structure differentiates between access to real-time data feeds, historical data archives, and route planning functionalities. While the number of requests is the primary metric, higher tiers may also unlock access to premium data sources, enhanced support, or higher rate limits. All plans include access to Transport for Germany's core products: the Real-time GTFS-RT API, Historical GTFS data access, and the Route planning API, as detailed in the official Transport for Germany documentation.
Customers can monitor their API usage through a dedicated developer portal, which provides real-time analytics and alerts for approaching plan limits. This transparency aims to prevent unexpected charges and allows users to optimize their API consumption. Billing is typically handled on a monthly basis, with options for annual commitments that may offer discounted rates.
Plans and tiers
Transport for Germany offers several plans catering to different scales of operation. Each plan includes a specific allocation of API requests and features, with the flexibility to upgrade or downgrade as usage patterns evolve. The primary tiers are:
- Developer Plan: This free tier is designed for evaluation and small-scale development. It provides a limited number of requests per month to test the API functionalities without financial commitment.
- Basic Plan: The entry-level paid option, suitable for small to medium applications requiring consistent API access beyond the free tier's limits.
- Standard Plan: Aimed at growing applications and businesses that require a higher volume of requests and potentially more advanced data access or support.
- Enterprise Plan: Customized solutions for large organizations with high-volume requirements, dedicated support, and specific compliance or integration needs.
The following table provides a comparison of the key features and limits across the main plans:
| Plan | Monthly Price | Included Requests per Month | Overage Rate | Key Features | Best For |
|---|---|---|---|---|---|
| Developer Plan | €0 | 5,000 | N/A (no overages) | GTFS-RT access, Historical GTFS (limited), Route Planning (limited) | Prototyping, testing, small personal projects |
| Basic Plan | €49 | 50,000 | €0.001 per request | Full GTFS-RT access, expanded Historical GTFS, standard Route Planning API | Small businesses, startups, growing applications |
| Standard Plan | €199 | 250,000 | €0.0008 per request | All Basic features, higher rate limits, priority support, advanced analytics | Medium-sized applications, mobility service providers |
| Enterprise Plan | Custom | Custom (millions+) | Custom | Dedicated infrastructure, 24/7 support, custom data feeds, bespoke SLAs | Large enterprises, government agencies, mission-critical applications |
Further details on each plan, including specific feature breakdowns and up-to-date pricing, are available on the official Transport for Germany pricing page.
Free tier and limits
The Developer Plan serves as Transport for Germany's free tier, offering a foundational level of access to its API capabilities. This plan is specifically designed to allow developers to explore the platform, build prototypes, and integrate basic functionalities without incurring any costs. The primary limit for the Developer Plan is 5,000 API requests per month. Once this limit is reached, API calls will typically return an error or be throttled until the next billing cycle, rather than incurring overage charges.
Key features accessible within the Developer Plan include:
- Access to the Real-time GTFS-RT API for live public transport updates.
- Limited access to historical GTFS data, suitable for basic analysis.
- Functionality of the Route Planning API, with potential restrictions on complexity or number of Waypoints per request.
This free tier provides sufficient resources for testing API endpoints, developing proof-of-concept applications, and understanding the data structure. For projects requiring consistent or higher-volume access, upgrading to a paid plan is necessary. Developers can monitor their usage through the Transport for Germany developer portal, which tracks request counts against the monthly allowance.
Real-world cost examples
To illustrate how Transport for Germany's pricing model translates into actual costs, consider these common use cases:
Example 1: Small Mobility App
A startup develops a mobile application providing real-time bus arrival predictions for a single city. Their app makes an average of 1,000 real-time GTFS-RT API requests per day to update bus positions and estimated arrival times for users. This totals approximately 30,000 requests per month.
- Plan required: Basic Plan (€49/month)
- Included requests: 50,000
- Usage: 30,000 requests
- Monthly cost: €49 (within plan limits)
- Rationale: The Basic Plan comfortably covers the app's current daily usage without incurring overage fees.
Example 2: Logistics Optimization Platform
A logistics company integrates the Route Planning API to optimize delivery routes for its fleet. They perform approximately 7,500 route calculations daily, which translates to 225,000 requests per month. They also access historical GTFS data for post-route analysis, adding another 10,000 requests per month.
- Total monthly usage: 235,000 requests
- Plan required: Standard Plan (€199/month)
- Included requests: 250,000
- Usage: 235,000 requests
- Monthly cost: €199 (within plan limits)
- Rationale: The Standard Plan is suitable for this volume, offering headroom before overages.
Example 3: Urban Planning Analytics Tool
A government agency uses Transport for Germany's historical GTFS data extensively for urban planning and traffic flow analysis. Their analytics tool runs daily batch jobs, consuming 5,000 GTFS-RT requests for current status and 300,000 historical data requests for deep analysis each month.
- Total monthly usage: 305,000 requests
- Plan considered: Standard Plan (€199/month)
- Included requests (Standard): 250,000
- Overage: 55,000 requests (305,000 - 250,000)
- Overage cost: 55,000 * €0.0008 = €44
- Total monthly cost (Standard with overage): €199 + €44 = €243
- Alternative: For consistent usage above 250,000 requests, moving to an Enterprise Plan might be more cost-effective if higher volumes are anticipated, or if dedicated support and custom features are required.
These examples highlight how usage patterns directly influence the optimal plan choice and potential monthly expenditure. The Google Maps Platform offers a similar pricing calculator, which can be a useful comparison for estimating API costs based on anticipated usage.
How the pricing compares
Transport for Germany's pricing model aligns with industry standards for public transit and mapping API providers. Its request-based structure is common, as seen with alternatives like Google Maps Platform.
- Google Maps Platform: Offers a pay-as-you-go model with a monthly free tier (e.g., $200 free credit per month for various APIs), after which costs are incurred based on usage of specific APIs like Geocoding, Directions, or Places. Their pricing can vary significantly based on the API endpoint used and volume. Transport for Germany's tiered approach with bundled requests offers more predictable costs for defined usage levels, particularly for public transit specific data (Google Maps Platform pricing details).
- Moovit & Transit (App): These are primarily consumer-facing applications rather than direct API providers for public transit data. While they may offer enterprise solutions, their core business model and pricing strategies are not directly comparable to Transport for Germany's developer-focused API pricing. Moovit, for instance, focuses on B2B solutions for smart mobility and urban transit, often involving custom contracts rather than transparent tiered API pricing.
Transport for Germany's differentiator lies in its specialization in German public transport data, which may offer more granular or specific data sets compared to broader mapping platforms. The tiered pricing with clear monthly request allowances aims to provide transparency and cost control for developers and businesses focusing on the German market. The free developer tier is competitive, offering a reasonable threshold for initial development compared to some alternatives that might require credit card details upfront even for minimal usage.