Île-de-France Mobilités Open Data (PRIM)

What you can build

• Slip the hotel shuttle to the next RER

  Poll stop-monitoring for the station your shuttle meets. When the estimated arrival moves, the operator proposes the new shuttle slot and stores the SIRI Lite response it used.

  With Shuttle Timing

• Staff up when a line goes BLOCKING

  Read the Traffic Info Messages global query. When a disruption with severity BLOCKING touches the lines your customers or staff use, the operator proposes an intraday staffing change and quotes the message.

  With Intraday Balance, Event Surge

• Tell arriving guests which elevator is out

  Match the guest's arrival station to État des ascenseurs. When an elevator on their route is out of service, the operator proposes a pre-arrival note for your approval.

  With Arrival Prep

Requirements

• A PRIM account; the token is shown in full only once and a new one makes the old one obsolete
• The stop and line ids from the referentials, since MonitoringRef and line ids follow the STIF naming
• Accept-encoding gzip, deflate on the global Next Departures query, which is served compressed
• Requests smoothed over time; quotas apply per second and per day, and the My API Usage page is where you ask for more

Authentication

A PRIM account whose token, generated once on the My authentication tokens page, is sent as the API key header on every request.

Limits

• Real-time next departures cover only part of the network; the perimeter dataset lists which stops and lines are included and is updated weekly
• Tokens generated from March 2024 carry 5 requests per second and 1,000 per day on each of the Next Departures and Traffic Info APIs
• Licences differ by dataset: Licence Ouverte for referentials, ODbL for offer and validation data, CC BY-NC-ND for maps, Licence Mobilité on the GTFS
• Portal, documentation, and licence pages are in French, with a machine-translated English view

Questions and answers

Which quotas apply to the real-time APIs?

Each API page prints its own table. For tokens generated after March 13, 2024: 5 requests per second and 1,000 per day on the unitary stop-monitoring call, the global estimated-timetable call, and the Traffic Info global query. Older tokens carry higher daily ceilings. Increases are requested on the My API Usage page.

How often is the GTFS republished?

Three times a day, at 8h, 13h and 17h. The files describe the planned offer for the next 30 days for every line in Île-de-France, consolidated from 75 operators across the OPTILE, RATP and SNCF networks. The dataset carries the Licence Mobilité.

What format do the Next Departures APIs use?

SIRI Lite, as the service description states. Timetable fields use the format yyyy-mm-dd'T'hh:mm:ss.SSSZ. The unitary call takes a MonitoringRef for one stop; the global call returns every stop currently available in one exchange and should be requested with gzip.