Sell your tickets through Entur
Callbacks and events
Sending updates through callbacks and events
If something changes on your end, and it affects the tickets a traveler has purchased through Entur, we should be notified through a callback or an event. This will allow us to present up-to-date information to the traveler. Examples of changes that needs notification:
- A change of departure, when the traveler is moved to another timetabled departure
- A change of seat or berth, when the traveler is moved to another place in the bus or train
- Changes to personal information, when relevant personal information about the travelers is updated on your end
When one of these notifications are received, Entur will then fetch updated data from your API, ensuring that what we show to the traveler is accurate and up to date.
Changes to departure times due to delays or changes to the service journeys are handled through the timetable data and does not need to be notified for each purchase. If the traveler is moved to another departure (with a different ID), then we must be notified.
Last modified on
Did you find what you were looking for?