SNCF Railway Transport France Pricing: Plans & Costs (2026)

Pricing overview

SNCF's Railway Transport for France API pricing structure offers tiered access designed to accommodate various usage levels, from individual developers to enterprise-scale applications. The model is subscription-based, with different plans providing increasing daily request limits. This structure allows users to select a plan that aligns with their operational needs, ensuring scalability as their application grows. The primary determinant of cost is the volume of API requests an application makes daily, with higher tiers offering more requests for a fixed monthly fee. For a comprehensive breakdown of the official pricing details, refer to the SNCF Developer Pricing page.

The pricing strategy prioritizes predictable monthly costs, which can be beneficial for budgeting and financial planning for projects relying on consistent API access. Users are typically charged a flat monthly rate for their chosen tier, with the option to upgrade or downgrade as their requirements change. This approach contrasts with pay-as-you-go models, where costs can fluctuate significantly based on actual usage. The provided plans include a free Sandbox tier, followed by several paid tiers that offer progressively higher request allowances and potentially additional features or support levels, although specific feature differentiators beyond request volume are not explicitly detailed in the public pricing summary.

Understanding the request limits associated with each tier is crucial for developers when estimating costs and selecting an appropriate plan. Exceeding daily limits may result in rate limiting or require an upgrade to a higher tier to maintain service continuity. Therefore, developers should monitor their API usage closely to avoid service interruptions and optimize their expenditure. The structured pricing aims to support a wide array of use cases, from personal projects testing the API's capabilities to commercial applications requiring substantial and reliable access to French railway data.

Plans and tiers

SNCF offers a clear progression of API access tiers, each tailored to different development and operational scales. These tiers are primarily distinguished by their daily request limits and associated monthly costs.

The available plans are:

• Sandbox: This is the free tier, ideal for initial development, testing, and proof-of-concept projects. It provides a foundational level of access without financial commitment.
• Starter: The entry-level paid tier, designed for small-scale applications or those in early production. It significantly increases the daily request allowance compared to the Sandbox.
• Growth: Positioned for applications experiencing moderate user growth or requiring more frequent data updates. This tier offers a higher request limit than Starter.
• Enterprise: Tailored for large-scale commercial applications, high-traffic services, or organizations with extensive data integration needs. This tier provides the highest request limits and may include custom support options.

The following table outlines the key characteristics of each plan based on publicly available information:

It is important to note that for the Growth and Enterprise tiers, specific pricing and exact request limits are generally subject to direct consultation with SNCF's developer relations team. This allows for customized solutions that can accommodate unique operational demands and potential service level agreements (SLAs).

Free tier and limits

SNCF provides a free Sandbox tier for developers, which is an essential entry point for anyone looking to integrate with the Railway Transport for France API. This tier is designed to facilitate initial exploration, development, and testing without any financial commitment.

Key features and limits of the Sandbox tier:

• Daily Request Limit: Users on the Sandbox tier are permitted up to 1,000 API requests per day. This limit is generally sufficient for individual developers or small teams to build and test core functionalities of their applications.
• Access to Core Products: The Sandbox tier typically grants access to the fundamental APIs, such as train schedules, real-time traffic, and journey planner functionalities. This allows developers to fully understand the API's capabilities and data structures.
• No Cost: The primary advantage is the zero-cost barrier to entry, enabling developers to experiment and innovate without upfront investment.
• Rate Limiting: Upon reaching the 1,000-request daily limit, subsequent requests will likely be rate-limited or rejected until the next 24-hour cycle begins. Developers should implement robust error handling in their applications to manage these limits gracefully.

The Sandbox tier is particularly useful for:

• Prototyping: Quickly building and testing new ideas or features that rely on French railway data.
• Learning and Experimentation: Familiarizing oneself with the API's structure, endpoints, and response formats using HTTP status codes and JSON payloads.
• Demonstrations: Creating small-scale demonstrations or proof-of-concept applications before committing to a paid plan.

While the Sandbox tier is comprehensive for testing, it is not intended for production environments that require sustained, high-volume API access. For any application moving beyond initial development or serving a user base, transitioning to a paid tier like Starter or Growth becomes necessary to ensure reliable performance and avoid hitting daily limits during peak usage.

Real-world cost examples

To illustrate how SNCF's API pricing translates to actual development costs, consider the following scenarios:

Scenario 1: Personal Journey Planning App (Free Tier)

• Application Type: A personal mobile app that allows a user to look up train schedules and plan a few journeys per day.
• API Usage: The app makes approximately 50-100 requests per day for schedule lookups and journey planning.
• Cost: €0 per month. The app comfortably stays within the 1,000 requests/day limit provided by the Sandbox tier. This is suitable for hobby projects or very low-traffic internal tools.

Scenario 2: Small Business Travel Management Tool (Starter Tier)

• Application Type: An internal web application for a small company to manage employee train travel bookings and track real-time train status for business trips across France.
• API Usage: The application averages 1,500 requests per day for various employees checking schedules, delays, and booking information. On peak days, it might reach 3,000-5,000 requests.
• Cost: €50 per month. The Starter tier offers 50,000 requests per day, which is more than sufficient for this usage pattern, providing ample buffer for peak days without incurring overage charges or hitting limits.

Scenario 3: Regional Public Transport Information Kiosk (Growth Tier Estimate)

• Application Type: A network of public information kiosks in a French city providing real-time train departure and arrival information, as well as local journey planning options.
• API Usage: Each kiosk might make requests every 30 seconds for real-time updates, plus additional requests for user-initiated journey planning. Collectively, the kiosks generate an estimated 200,000-500,000 requests per day.
• Cost: Requires contact with SNCF for Growth or Enterprise tier pricing. At this scale, the Starter tier (50,000 requests/day) would be inadequate. A custom plan would be negotiated to accommodate the high volume and potentially provide dedicated support or higher reliability guarantees. Pricing would likely be significantly higher than the Starter tier, reflecting the increased infrastructure and service requirements.

These examples highlight that for modest usage, the free tier is highly effective. As usage scales beyond small-scale operations, a move to the Starter plan offers a cost-effective solution for many business applications. Larger, production-grade systems necessitate direct engagement with SNCF for tailored pricing and support, demonstrating a common practice in cloud service and API pricing models.

How the pricing compares

When evaluating the pricing of SNCF's Railway Transport for France API, it's useful to compare it against alternatives in the broader rail transport API market. While direct one-to-one comparisons can be challenging due to varying feature sets, geographical coverage, and pricing models, a general understanding of the landscape can be formed.

Key competitors and their general pricing approaches include:

• Deutsche Bahn (Germany): Deutsche Bahn offers its own developer portal, the DB Open-API platform, which provides data similar to SNCF for German rail transport. Their pricing models often include free tiers for development, with paid tiers structured based on request volume or specific data access levels. The specific cost per request or monthly fee can vary, but the model is generally comparable to SNCF's, focusing on subscription-based access tied to usage limits.
• Transport for London (UK): TfL's API for London transport data is often noted for its relatively open access. While it primarily covers urban transport within London rather than national rail, it provides a benchmark for public sector-driven APIs. The TfL API is largely free for typical developer usage, with very high limits that rarely require payment unless for extremely high-volume commercial applications requiring custom arrangements. This represents a more permissive free-tier approach than SNCF's 1,000 requests/day limit.
• Transitland (Global): Transitland, an open data platform, aggregates public transit data from various sources worldwide. While not a direct operator API, it offers a broad dataset. Its pricing model typically leans towards open data principles, with usage often free or community-supported for standard access. For large-scale commercial redistribution or custom data needs, specific licensing or premium services might apply. This positions Transitland as a potentially lower-cost alternative for projects that can leverage aggregated, standardized data rather than real-time, operator-specific feeds.

SNCF's Competitive Position:

• Predictable Costs: SNCF's subscription-based model with fixed monthly fees for defined request limits offers predictable costs, which can be advantageous for budgeting compared to purely usage-based models where costs can fluctuate.
• Regional Focus: Its strength lies in its authoritative and real-time data for French railway transport, making it an essential choice for applications specifically targeting France. Alternatives might cover broader geographies but potentially lack the depth or real-time accuracy for a specific national rail network.
• Free Tier Adequacy: The 1,000 requests/day free tier is standard among many API providers, generous enough for development but typically requires an upgrade for production. This is less permissive than some public transport APIs like TfL, but more structured than completely open data initiatives.
• Scalability: The tiered structure allows for clear scalability, from the Starter tier (€50/month for 50,000 requests/day) upwards to custom Enterprise solutions, ensuring that applications can grow without hitting rigid ceilings.

In summary, SNCF's pricing is competitive within the landscape of national rail operator APIs. It strikes a balance between providing a free entry point for developers and offering scalable, predictable paid tiers for commercial applications, aligning with common practices seen across the API economy, as detailed by various web service standards and pricing trends.