Subscriptions

Add new Subscription

Find valid ids for stop places and quays at stoppested.entur.org. Only stops based on national ids will be handled by ukur (ie. starting with "NSR:").

New subscriptions will receive push messages after these rules:

ET messages: If a subscription has one 'From stop' and one 'To stop' affected and in correct order or the journey regards a subscribed LineRef in an EstimatedVehicleJourney with delays/cancellations, the entire EstimatedVehicleJourney is pushed after unsubscribed stops/lines are removed to minimize the message size. If codespace(s) is specified, and not limited by stops/lines, the EstimatedVehicleJourney is pushed if it comes from that codespace (as indicated by DataSource).
SX messages: If one of the stops or line from a subscription is affected by a PtSituationElement, the entire PtSituationElement is pushed after affects not regarding the subscription are removed. If codespace(s) is specified, and not limited by stops/lines, the PtSituationElement is pushed if it comes from that codespace (as indicated by participantRef).

This demo application uses json to add and delete subscriptions. There is also a XML format from the SIRI specification that does not support all attributes from the json format.

Name

(Not valid/supported when using XML - but required when using json like we do here.)

From Stops

To Stops

LineRefs

Codespaces

Type

Deviation Type

SIRI Subscription Model

Whether the push messages should be wrapped in a Siri element according to the SIRI specification or simply be root element themself.

Heartbeat Interval

Must follow the W3C XML Schema 1.0 Duration format. Ex PT10M is every 10th minute.

Minimum delay duration

Must follow the W3C XML Schema 1.0 Duration format. Ex PT30M send push message if arrival or departure is delayed more 30th minute.

Refresh page

Add new Subscription

build-name: ukur-demo, build-version: 1.0.33, build-time: 2026-09-21T11:32:18.472