Use NOD

Agreements

PTOs must make an agreement with Entur on the use of NOD, on behalf of their system suppliers. The PTO will then have access to the necessary passwords to use NOD. A third party who, for example, wants to sell products in combination with collective tickets will have to make an agreement with a PTO and call services at this PTO. Only PTOs call NOD directly.

Technical

The system vendors must have access to NOD to place orders, and get a password for their NOD Clients.

Customize your own sales solution

A PTO must integrate its sales solution with NOD Backoffice.

Develop NOD client

A PTO must develop its own NOD Clients alone, or in cooperation with other PTOs. In this development work, one can greatly benefit from the NOD Client API developed for this purpose.

Establishing transaction flow

The PTO must decide how the results of NOD Pickups are to be communicated (whether transaction flow is necessary or not). It must then be agreed with Entur how these transactions should be retrieved.

Develop your own plugins

Most products should be covered by existing Plugins. For special needs, separate plugins can be developed by the PTO itself. These can then be linked to NOD by agreement with Entur.

Reusable libraries

A reference JAVA API is being developed for NOD clients (Android, Javascript (Native) and stationary). This can be used to get started quickly with NOD Client development.

Tickets Check

To check a ticket, the control unit must have a copy of the keys needed to verify the contents of the ticket medium. This is today's key on mobile tickets and the read key to travel cards. Contact Entur to access this. NOD can check a ticket using the Inspection plugin.