Implement new Oracode/Kaba API

Lockmaker Oracode/Dormakaba/Kaba has just released their new API which allows for integration with their locks. The current implementation lacks several features that are core parts of Stay n Touch functionality (in addition to requiring a dedicated PC on-site to handle code creation). The current state is:

  • Only guests who use the self check-in can receive room numbers and codes from the system automatically
  • Upsell features like early check-in or late check-out are unable to be used as the integration in its current state cannot pull the appropriate codes that will unlock doors early/late
  • Rover is unable to generate codes through its own UI; front desk must go to the Kaba E-code Wireless website to generate codes for all guests who don't use pre check-in which is time consuming and slows down the check-in process significantly. Ideally the blue "Key" button on the stay card would generate a code for the assigned room & dates using the Rover UI without having to go to another website.

By coding to the new API, Rover should be able to address all of these shortcomings in the current implementation (including, hopefully, not needing a dedicated PC to generate codes for guests who use the self check-in). 

Please contact Marc Chami at marc.chami@dormakaba.com for information about the API and the NDA required to access it.

Building this integration with the new API would complete the Oracode/Kaba integration and allow us to use the upsell functionality of early check-in and late check-out which we are currently unable to offer to our guests.

2 CommentsSorted by Oldest First
Forum User

Wanted to update this as Rover can pull codes for guests (it was a setting that didn't get turned on during our implementation for some reason but is on now).

That said, the point about generating early check-in codes is still valid as the system can only pull regular check-in codes.

Further, because the current integration relies on a single Windows PC located on our property, if this machine has an issue (doesn't start up after security updates, power outage, internet outage, etc.) then none of the guests get codes generated during the auto check-in process. The system will still send out the check-in emails but the codes are not included. 

If the integration used the API instead of a local PC it would be substantially more robust than it is currently.

Forum User

Just checking in on this request. Would be a win for everyone using Kaba and make implementation much easier as you wouldn’t need to remote into a Windows PC to configure. Also, we had a power outage recently and that means no guests get assigned door codes: would be much better to have this handled by servers in a data center vs a single point of failure machine here on-site.

Login or Signup to post a comment