Partner services
Sales v2
Entur's new and recommended interface for ticket sales in the Entur platform.
Access requirements
- Partnership agreement with Entur (email us)
- Client identification (ET-Client-Name)
- OAuth 2.0 authentication
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,StopPlaceandTripPatternreferences 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
GETalways 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 need | Use |
|---|---|
| Trip suggestions or place lookup in your own client | Journey Planner and Geocoder |
| Receipts | Receipt API |
| Third-party products | Third 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 libraries | Account-based ticketing |
| Shared mobility, such as e-scooters and bikes | Shared mobility |
| The OSDM standard | Entur has a separate OSDM compatibility layer: OSDM |
About OMSA
Sales v2 is based on the Open Mobility Sales API (OMSA) specification.
Next steps
Last modified on
Did you find what you were looking for?