Connect booking channels, payment services and other business systems to your ferry operation. Select integrations around a defined workflow and ownership of the data.
Agree which system owns routes, fares, bookings and payment references. This prevents two applications from maintaining conflicting versions of the same commercial information.
The actual online-booking views show departure selection and ticket choice. They illustrate the passenger-facing booking flow that can be linked from your website. API scope and other system connections are defined for the integration being implemented.
The original sale and a later amendment may start in different systems. Decide which system owns the booking, how the external reference is retained and who handles the passenger request. Payment references, ticket delivery and available capacity must be considered in the same exchange, even where several providers are involved.
Use the configured online shop, a supported partner connection or an API project as appropriate. An available API is not a promise that every external product is connected without implementation work.
Rehearse a successful transaction, a rejected booking and a delayed update. Check how the sales team can identify and resolve a transaction that needs attention.
Connect external software to Travelmanager through the available interfaces.
Explore API
Connect payment providers, sales channels and the systems your team uses.
Explore Integrations & Partners
Add Travelmanager online booking to your own website.
Explore Website Integration
An API integration is a business hand-off implemented through software.
Explore Ferry Booking API Integration
Explore Travelmanager’s ferry software features: schedules, passenger and vehicle bookings, ticket sales, boarding, reporting and integrations.
Explore FunctionsTell us how api & integrations fits into your operation and which part you want to improve. We’ll review the relevant workflow and the scope of your setup with you.
