These APIs allow your server to subscribe to real-time data from all included real-time feeds in Norway on SIRI 2.0. It is available as SIRI XML, SIRI Lite (REST) and GTFS-RT.
These services include only real-time data and not any basic journey planner information. If you are creating an end-user service such as a journey planner, the JourneyPlanner API is a better choice.
Available data streams
Troms og Finnmark (Snelandia)
Møre og Romsdal (Fram)
Vy/Flytoget/Go-Ahead/SJ Nord (via Bane NOR)
Oslo region (Ruter)
Vestfold og Telemark (Farte)
Troms og Finnmark (Troms fylkestrafikk)
Vestfold og Telemark (VKT)
Viken (Østfold kollektivtrafikk)
SIRI is a CEN Technical Standard that specifies a European interface standard for exchanging information about the planned, current or projected performance of real-time public transport operations between different computer systems.
When using publish/subscribe you'll first get one (or more) set with initial data, and then continuous updates with changes. This option requires an accessible endpoint which accepts HTTP POST requests from the Entur SIRI service.
For Request/Response, the <RequestorRef> attribute is used to track changes and must therefore remain the same for all subsequent requests in order to only get changes. The attribute MoreData=true means the data comes in bunches, just like paging, and more data can be fetched immediately after the first "page" is received. Eg. if there are 20,000 objects, these will be split up in smaller parts and repeated requests are needed to get the full set.
Types of data
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
Textual messages displayed to end users. They are always associated with a departure, line, stop etc., or combinations of these.
With simple HTTP GET calls to retrieve data, you can use the requestorId URL-parameter to only retrieve changes made since the last time you asked. If you do not use this, you will always get the full dataset, not just the first time you make a request. You must use a unique UUID.
GTFS Realtime is a feed specification that allows public transportation agencies to provide realtime updates about their fleet to application developers. It is an extension to GTFS (General Transit Feed Specification), an open data format for public transportation schedules and associated geographic information.
Only supports request/response currently. Endpoints exist for each data type that download the full dataset, filtered by datasource (codespace) if provided. This dataset is updated every 15 seconds. Later we will support publish/subscribe and continuous updates.