How do booking systems connect to mobile cabin keys?
FLEXIPAX connects reservation information to mobile cabin-key delivery through its open API, while the SDK adds mobile-key functionality to a native passenger app. FLEXIPAX works with supported Bluetooth lock systems from ASSA ABLOY VingCard, Salto and other providers. Compatibility depends on the manufacturer, model, firmware or door-lock software and available integration; Bluetooth alone does not confirm support.
External reservation systems connect through the FLEXIPAX open API. The booking workflow, lock integration and passenger delivery requirements determine the implementation scope and timeline.
For a proprietary reservation system, your technical team and FLEXIPAX agree how booking information connects to key creation and delivery. Use the API for system communication and assess the SDK if mobile keys belong inside your own native passenger app.
Prepare the reservation-system details, passenger-app requirements, cabin-lock model and software version for a technical integration review.
How does the FLEXIPAX mobile-key API work?
The FLEXIPAX API connects internal or external reservation systems to mobile-key creation and delivery. Configured delivery options include text, email or an operator's own solution. A delivery message is not itself a Bluetooth cabin key: passengers follow the configured process to download their credential.
How does the FLEXIPAX SDK fit into a passenger app?
The FLEXIPAX SDK lets developers include mobile-key functionality in their own native passenger app. FLEXIPAX supports onboarding and coordination with door-lock providers on certification requirements. Review the app, lock model and software together before implementation.
FAQs
What is the difference between the mobile-key API and SDK?
The API connects booking systems to mobile-key services. The SDK adds mobile-key functionality to a native passenger app. An operator may use both, depending on its systems and passenger experience.
Which events and fallback cases should an integration cover?
Agree when a key is created, how passengers receive it and how cabin changes and checkout are handled. Test downloading and updating keys with connectivity, opening doors with a downloaded key offline and reception fallback when a phone is unavailable.
Can we use the same integration across several vessels?
FLEXIPAX connects booking systems, mobile-key delivery and compatible cabin locks for cruise and ferry fleets. Review the locks, software, reservation systems and passenger apps on each vessel before agreeing a rollout. Plan cabin changes, reception support and physical-keycard fallback with the operations team.
Where can developers discuss API access and requirements?
Contact FLEXIPAX with your reservation system, passenger app, lock manufacturer and model, and integration goals. The team can discuss API or SDK access, documentation and compatibility requirements for your project.