Two building blocks. The API connects your reservation system. The SDK puts the mobile key inside your own passenger app.
Internal or external booking system
Creates and delivers mobile keys
Your app with the SDK, or the FLEXIPAX app
ASSA ABLOY VingCard, Salto and other supported locks
Downloading or updating a key needs data. Opening the door doesn’t.
Server to server
Connects your reservation system to key creation and delivery.
Inside your app
Adds mobile-key functionality to your own native passenger app.
Use both when bookings come from your systems and the key belongs in your own app. See the SDK in a passenger app
Your reservation system holds the stay.
Through the FLEXIPAX API, for example after embarkation. You agree the trigger.
In your app with the SDK, or by text or email.
The phone fetches the mobile key.
Needs dataBluetooth at the lock, no internet needed.
Works offlineAn updated mobile key replaces the old one. Reception can issue a card meanwhile.
Needs dataThe mobile key stays valid until checkout date and time.
Send us these details and the technical review starts with the right answers.
{
"vessels": "fleet size and vessel types",
"reservation_system": "internal or external, which vendor",
"passenger_app": "own native app (SDK) or none yet",
"key_delivery": "in-app, text or email",
"lock_vendor": "e.g. ASSA ABLOY VingCard, Salto",
"lock_model": "model and Bluetooth capability",
"lock_software": "door-lock software or firmware version",
"connectivity": "on-board data for key downloads"
}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.
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.
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.
External reservation systems connect through the FLEXIPAX open API. For a proprietary reservation system, your technical team and FLEXIPAX agree how booking information connects to key creation and delivery. The booking workflow, lock integration and passenger delivery requirements determine the implementation scope and timeline.
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.
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.
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.
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.
Share your vessel or fleet size, cabin-lock model, reservation system and passenger app. The demo covers compatibility, API or SDK integration, key delivery and physical-keycard fallback.
Book a marine mobile-key demo