Entur Developer
Partner services

Sales v2

Entur's new and recommended interface for ticket sales in the Entur platform.

Access requirements

What Sales v2 does

Sales v2 combines the main features of the Offers, Orders, Reserve Offers, Ticket Distribution, Refund, Seating Manager, Seatmap, Products, Customers, and NOD APIs. You no longer need to integrate with each of them separately.

Sales v2 takes over work that partners previously did themselves:

  • Search: search directly with coordinates and addresses, without resolving place IDs first. Or search with the same FareZone, StopPlace and TripPattern references you are used to. Recommendations and bundling is configurable with useful defaults.
  • Purchase: prepare a package with one or two calls. Add offers, additional products and more while the package is in draft, then proceed to payment whenever you are ready.
  • Tickets: Sales v2 distributes and fetches travel documents on your behalf and rotates period tickets automatically. A single GET always returns the current travel documents. For now, we fetch NOD and PDF tickets on your behalf, but you would still need to integrate with Account-Based Ticketing separately.
  • Changes and cancellations: move tickets, update validity window, refund customers and more. The API tells you which options are available for any given package.
  • Customers: create and manage customers through the same API, with support for external references so you can keep a customer record in sync with your own. If you don't require customer profiles, you can still purchase anonymous travel documents and link them to customers in your own system.

What Sales v2 does not cover

You needUse
Trip suggestions or place lookup in your own clientJourney Planner and Geocoder
ReceiptsReceipt API
Third-party productsThird Party Product API
Payment (optional)Entur's Payment API, or your own payment provider with imported payments. Sales v2 returns links to the payment endpoints you need.
Account-based ticketing with the ABT client librariesAccount-based ticketing
Shared mobility, such as e-scooters and bikesShared mobility
The OSDM standardEntur has a separate OSDM compatibility layer: OSDM

About OMSA

Sales v2 is based on the Open Mobility Sales API (OMSA) specification.

Next steps

Documentation

New sales integration
Building a sales integration with Entur for the first time? Understand the sales lifecycle and find the guides for your use case.

Documentation

Migrating from Entur's existing sales APIs
Already selling through the Offers, Orders, Ticket Distribution, or Refund APIs? See where each step ends up in Sales v2.

Guide

Sales v2 guides
Step-by-step instructions, from your first search to a confirmed purchase.

API reference

Sales v2 API reference
The full list of processes and collections.
Last modified on
Did you find what you were looking for?