Reference · built on requestCommons signalTransit, roads & mobility

API SNCF

Scheduled and real-time SNCF train departures, arrivals, disruptions, and journeys through the Navitia-based API SNCF.

Request accessPricing ↗

About

API SNCF is the SNCF group's developer API at api.sncf.com/v1, built on Navitia, the open-source journey engine from Kisio Digital. The sncf coverage carries planned and real-time times for TGV, Intercités, TER, Lyria, and Eurostar trains; Transilien appears with planned times only. The SNCF FAQ names four jobs: train journeys from one station or town to another, next departures and arrivals at a station, line timetables, and station name search.

On Fibric, an operator reads the next passages and the disruptions for the stations you care about and proposes a shuttle change, an arrival update, or a no-show explanation for your approval, with the disruption message attached.

This is a reference listing. It documents what Fibric would read from API SNCF and what it could propose, based on the publisher's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • departures and arrivals at a stop_area, with data_freshness set to realtime or base_schedule
  • disruptions with an effect such as SIGNIFICANT_DELAYS, REDUCED_SERVICE, NO_SERVICE, MODIFIED_SERVICE, or ADDITIONAL_SERVICE
  • journeys between two places on the sncf coverage, combining several trains
  • stop_schedules, terminus_schedules, and route_schedules for a line's timetable grid
  • places and pt_objects autocomplete on station names, and places_nearby for the closest station to a point
  • coverage, lines, stop_areas, and stop_points to explore the network objects the other calls reference

Proposed actions

Read-only. This feed informs operators; it changes nothing.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Prepare the room for the train that is running late

    Read the real-time arrival for the guest's train at your nearest station. When it slips, the operator proposes a later room-ready target and a front-desk note that quotes the new time.

    With Arrival Prep

  • Hold the station shuttle for the delayed TGV

    Poll departures and arrivals for the station your shuttle serves with realtime freshness. The operator proposes a new shuttle slot and leaves a record of the delay it acted on.

    With Shuttle Timing

  • Explain a no-show with the disruption on file

    When a shift starts without its worker, check the disruptions on the TER lines they commute by. If a NO_SERVICE or SIGNIFICANT_DELAYS effect covers that window, the operator proposes the cover shift and attaches the message.

    With No-Show Response

Requirements

  • A developer token requested with your first name, last name, and email, after accepting the API SNCF terms of use
  • The stop_area ids of the stations you watch, found through the places call
  • Request pacing within 5,000 requests per day; the FAQ says access is blocked for the remainder of the period once the quota is spent
  • An enterprise plan from SNCF if you need a higher volume or dedicated support
Authentication
A free developer token from the SNCF registration form, sent as the Basic authentication username with an empty password, in the URL, or in the Authorization header.

Limits

  • Trains only: no RATP metro, no bus, no coach, no bike data
  • The data window is -1/N/+23: the previous day through 23 days ahead, for every train in the API
  • Transilien trains carry planned times only; intra-Paris connections use approximate walking or transit durations
  • The developer quota is 5,000 requests per day, or 150,000 per month

Access and pricing

Reference listing. Public feed access is separate from Fibric integration. If you request this feed, your quote covers the build, usage, and support.

Request API SNCF ↗

Questions and answers

Which trains carry real-time data?
The FAQ lists TGV, Intercités, TER, Lyria, and Eurostar with both planned and real-time times. Transilien timetables are planned only. Metro lines run by RATP are outside the API, as are buses, coaches, and bikes.
What happens when I pass 5,000 requests in a day?
Access is blocked for the remaining part of the period. The FAQ gives the example of a user who spends the daily quota in twelve hours and is blocked for the next twelve. Enterprise plans carry a custom volume.
Where is the API documented?
In the Navitia documentation at doc.navitia.io, which describes journeys, departures, arrivals, stop_schedules, route_schedules, places, disruptions, and the data_freshness parameter. SNCF points to playground.navitia.io to build and test requests, and to its FAQ and support form for questions.
Ask about API SNCF

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This Commons signal listing is developed, published, and supported by Fibric. It reads public data published by SNCF (api.sncf.com), documented by Navitia (doc.navitia.io). Upstream agencies and projects are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy