Real-time information

Entur harvests real-time data from all available sources in the Norwegian public transport sector and repackages the data in a unified format (SIRI 2.0, available as SIRI XML or SIRI Lite ReST). The data is divided into "codespaces" which represent the respective data sources. For how to use the data, see this example: https://api.entur.io/realtime/v1/rest/sx?requestorId=345345-23423423-324

 

SIRI Feeds

ET – Estimated Timetable

Real-time estimates for each service journey. Included are planned, actual and estimated departure times, cancellations and changes in stop patterns. 

VM – Vehicle Monitoring

Vehicle-centric real-time data with the position of a vehicle, as well as any deviation from scheduled timetable on a given departure.

SX – Situation Exchange

Text messages displayed to end users. May be associated with departure, line, stop, stretch, etc.

Real-time sources

Codespace Feed source SIRI ET SIRI VM SIRI SX
         
  All sources as one feed Yes Yes Yes
AKT Agder kollektivtrafikk (Aust- og Vest-Agder) Yes   Yes
ATB AtB (Trøndelag)   Yes Yes
AVI Avinor (Domestic air departures)      
BRA Brakar (Buskerud) Yes   Yes
FIN Snelandia (Finnmark)      
HED Hedmark-Trafikk (Hedmark) Yes    
KOL Kolumbus (Rogaland)   Yes Yes
MOR Fram (Møre og Romsdal) Yes   Yes
NOR Nordland fylkeskommune Yes   Yes
BNR NSB/Flytoget (via Bane NOR) Yes    
OPP Opplandstrafikk (Oppland) Yes    
NSB NSB     Yes
RUT Ruter (Oslo & Akershus) Yes Yes Yes
SOF Kringom (Sogn og Fjordane)      
SKY Skyss (Hordaland) Yes   Yes
TEL Farte (Telemark)      
TRO Troms fylkestrafikk Yes   Yes
VKT VKT (Vestfold)      
OST Østfold kollektivtrafikk Yes Yes Yes

Delta load/changes

Publish/subscribe

By using publish/subscribe you'll first a full set of data, and then a continuous stream of updates, as they occur.

Request/response

For request/response, the <RequestorRef> attribute is used to track changes, and must, therefore, be identical for all subsequent requests in order to receive only updates, rather than a new full dataset. If your request is for a large amount of data, the API may return the attribute MoreData=true. This means there is more data available, and you should repeat the request until you receive a MoreData=false status.

SIRI Lite

When making simple HTTP GET calls to retrieve data, the requestorId parameter should be used to retrieve only the changes that have occurred since the previous request with the same requestorId. If requestorId is not used, a full dataset will be retrieved every time.

enlightened Please use a unique UUID.

 

HTTP POST (Standard SIRI 2.0)

Publish/subscribe: https://api.entur.io/realtime/v1/subscribe

Request/Response: https://api.entur.io/realtime/v1/services

To get data for only one provider at a time, simply append the three letter codespace of your desired provider to the URL. A list of codespaces can be found in Quickstart.

HTTP GET (Standard SIRI 2.0 Lite)

HTTP GET https://api.entur.io/realtime/v1/rest/sx

HTTP GET https://api.entur.io/realtime/v1/rest/vm

HTTP GET https://api.entur.io/realtime/v1/rest/et

To get data for only one provider at a time, simply append the three letter codespace of your desired provider to the URL. A list of codespaces can be found in Quickstart.

ID-mapping

By default, the API returns ID's matching those in the static timetable data. To have the API return ID's matching the source data, add the URL-parameter useOriginalId=true. The same is possible for SIRI publish/subscribe and request/response.

enlightened Please note that although technically possible, these API's should NOT be used directly by an end-user-application. Instead, use the Journey planner API.