
Ferry Booking API
Connect a website, sales partner or internal system to the ferry booking workflow.
Explore Ferry Booking APIConnect external software to Travelmanager through the available interfaces. Start with the data exchange you need, then confirm which records, identifiers and endpoints support it in your installation.
A website booking, a partner sale, a timetable feed and an accounting export do not use the same data. List what must be sent or retrieved, which identifiers match the records and which system starts the exchange before implementation.
A timeout means the caller did not receive an answer in time. It does not confirm whether Travelmanager accepted the booking. An integration should use the agreed identifiers and lookup methods to check the recorded result before sending the transaction again. The exact endpoints and recovery behaviour must be confirmed for the installation.
Decide when data is exchanged and what should happen if an update fails. A retry must be checked against the result already recorded; do not assume that every timeout means that no booking was created.
Authentication, endpoint availability and supported fields are checked for your installation. Use a representative test transaction and reconcile the booking result, related positions and payment context before connecting production channels.

Connect a website, sales partner or internal system to the ferry booking workflow.
Explore Ferry Booking API
Connect booking channels, payment services and other business systems through defined interfaces.
Explore API & Integrations
Connect payment providers, sales channels and the systems your team uses.
Explore Integrations & PartnersTell us which data you need to exchange and which part of the process you want to connect. We’ll review the workflow, the relevant interfaces and the scope of your setup with you.