Entur Developer
Sales v2

Migrating from Entur's existing sales APIs

This page is for partners who already sell through Entur's existing sales APIs. It shows how each action maps to new endpoints in Sales v2.

What changes

Instead of calling and orchestrating several services, you call Sales v2 processes and collections, and Sales v2 handles the rest. See What Sales v2 does for the APIs it replaces.

Step-by-step mapping

StepExisting sales APIsSales v2
Search for offersOffers. You supply NeTEx IDs, configure recommendations, and bundle offers yourself.search-offers with sane defaults for recommendations and bundling. FareZone, StopPlace, TripPattern, GPS coordinates and addresses are supported. Just search with from, to and optionally via
Select offersOrders and Reserve Offers. You create the order or order lines yourselfselect-offers to create a package from a set of offers and start modifying it with ancillaries or assets. Or use the purchase-offers shortcut to go straight from offers to a purchasable package.
BuyOrders: unlock, reset, fail, and confirm.release-package if the user abandons the checkout, extend-expiry-time if they need more time, purchase-package once they are ready to proceed
PayPayment API or your PSP and imported payments.The same. Create a package in Sales v2 and make sure it is paid, and the system prepares the rest
Get the ticketTicket Distribution and NOD. You fetch and rotate tickets yourself.travel-documents collection with automatic refresh. Just GET the latest valid travel documents
Change ticket timeTicket Distributions. update-validities, then fetch a new distribution and ticket.update-travel-document-validity, the travel-documents collection updates too
Find allowed changesChange Optionschange-options collection
Reserve seats and assetsSeating Services (Seating Manager and Seatmap), mapped to order lines yourself.assign-asset process and assets collection
RefundRefundsrefund-options collection, claim-refund-option. cancel-package if package is non-refundable
Create a customerCustomerscustomers collection

You still call Journey Planner, Geocoder or NSR yourself when you need a TripPattern or trip suggestions client-side.

What stays the same

  • Payment stays outside the sales flow, with your PSP or the Entur Payment API.
  • The Receipt API and Third Party Product API stay separate.
  • You still need the ABT API if you use account-based ticketing.

Next steps

Follow the guides in order to see the new flow end to end.

Step 1

Search offers
Model who is travelling and get your first offers.

Step 2

Make your first purchase
Prepare, pay for, and confirm a package.

API reference

Sales v2 API reference
The full list of processes and collections.

Documentation

Existing sales APIs
Documentation for the APIs you use today.
Last modified on
Did you find what you were looking for?