Integration process
The Kisi Mobile SDK lets you embed access control directly into your own iOS or Android app. Instead of users needing the Kisi app, they unlock doors through your app using Kisi-powered credentials.
What you can build
- Tap to Unlock - users hold their phone up to a Kisi Reader to unlock, using BLE (iOS) or NFC (Android)
- Tap in-app - users unlock doors from a button inside your app, via the cloud
- MotionSense - users wave their hand in front of a Kisi Reader to unlock
How it works
The SDK handles the low-level communication between your app and Kisi Readers. For Tap to Unlock and reader restrictions, the SDK scans for nearby Kisi iBeacons, extracts the lock ID and one-time password from the BLE advertisement, and generates the proximity proof required by the unlock API. For Tap in-app, the SDK authenticates the user and sends the unlock request to the Kisi cloud.
Your app handles the user interface and unlock triggers. The SDK handles credential and hardware communication.
Hardware requirements
Tap to Unlock and MotionSense require a Kisi Controller and a Kisi Reader, both installed and connected to the internet. Tap in-app works with a controller only. See hardware requirements.
Getting access
Before integrating the SDK you need a partner ID from Kisi. See Request SDK Access to apply.
SDK repositories
Integration guides
Testing
Use the testing protocol provided with your partner ID to validate your integration before launch.
Support
Contact support@getkisi.com if you run into issues during integration.