How to integrate Kisi
Kisi offers multiple integration approaches to suit different use cases and technical requirements. This guide explains each integration method and helps you choose the right approach for your application.
Integration overview
Kisi integrations enable your application to manage access control for doors equipped with Kisi hardware. Depending on your needs, users can access doors through the native Kisi mobile app, your custom application, or automated workflows. The integration method you choose depends on factors like whether you need user-specific tracking, temporary or permanent access, custom mobile app functionality, or simple workflow automation.
1. API key integrations
The Kisi API provides several integration patterns for managing users and unlocking doors. Your application makes HTTP requests to Kisi's API endpoints to provision users, grant access, and trigger unlocks. The API integration approach you choose depends on whether you need individual user tracking, how users will unlock doors, and the complexity of your access control requirements.
Kisi API offers many more possibilities beyond what's specifically documented here. Our API reference provides comprehensive documentation of all available endpoints and resources that you can combine to build custom integrations tailored to your specific use case.
API user provisioning
This is the most common integration method. Your application creates user accounts in Kisi and grants them access to doors or groups. Users unlock doors through the native Kisi mobile app with full access to features like tap to unlock, MotionSense, and offline access. All unlock events are attributed to individual users for detailed audit trails.
Best for permanent user access with full access control features and individual event tracking.
Learn more about user provisioning →
API cloud unlocks
Your application makes direct API calls to unlock doors through admin credentials. No user provisioning or credential management required. Unlock events appear as admin actions in audit logs rather than being attributed to individual users.
Best for simple use cases where you need remote unlock capability without user-specific tracking.
Learn more about cloud unlocks
API access links
Your application generates time-limited access links with QR codes and web URLs. Users receive links via email and can unlock doors by scanning the QR code at readers or using the web link for remote unlocks. Access automatically expires after the defined period.
Best for temporary access scenarios like visitor management, delivery access, and temporary contractors.
Learn more about access links →
API unlocks on behalf of users
Your application creates a login on behalf of each user to obtain their credentials (secret). You then use this secret as the API key when making unlock requests, which attributes all unlock events to that specific user rather than an admin. Your app fetches each user's accessible locks and makes unlock requests using their credentials.
Best for custom unlock interfaces that need user-specific tracking while keeping unlock logic in your application.
2. SDK integration
The Kisi SDK allows you to embed access control functionality directly into your mobile application, creating a seamless single-app experience for your users. Instead of requiring users to download a separate Kisi app, they can unlock doors using your application with physical unlock methods like tap to unlock and MotionSense.
To integrate the SDK, your application must first provision users through the Kisi API to create their accounts and grant access permissions. Then, your mobile app integrates the Kisi SDK and initializes it with user login credentials. Once set up, users can tap their phone to a Kisi reader or use MotionSense to unlock doors without ever leaving your application.
The SDK is available only for native platforms (iOS and Android). There is no React SDK available at this time. This integration requires high implementation effort but provides complete control over the user experience and maintains full Kisi features including schedules, groups, and offline access. All unlock events are attributed to individual users for detailed audit trails.
This approach is best suited for organizations building custom mobile apps who want to provide physical access control as part of their core user experience. If you also need in-app cloud unlocks within your application, you can combine SDK integration with the API unlocks on behalf of users method described above. Additionally, the SDK can provide proximity proof functionality to satisfy reader restrictions when using API-based unlocks.
For detailed implementation steps, see the SDK integration process.
3. Marketplace app integration
Marketplace apps are integrations that can be configured directly from the Kisi web dashboard, rather than requiring users to configure the integration on your platform. Once listed in the marketplace, organization administrators can discover your integration in the integrations section and complete the entire setup process within the Kisi dashboard through a guided configuration flow.
Marketplace apps were previously exclusive to Kisi-built integrations. However, partners can apply to have their integration listed in the marketplace. This approach is ideal for creating pre-built connectors to popular platforms (such as fitness management systems, coworking software, or HR tools) that multiple Kisi customers need to use. The key benefits are that all Kisi customers will see your integration listed in their dashboard, making it easy to discover, and users can configure everything related to access control directly in the Kisi web dashboard, which significantly reduces friction.
If you believe your integration would benefit from marketplace listing, you can apply through our marketplace integration application form. This allows your integration to be listed on the integrations page in the Kisi web dashboard and enables users to configure it directly from there. Note that marketplace apps must meet specific quality and security standards and require approval from Kisi's team.
4. Zapier integration
If your platform has Zapier integration, you can connect it with Kisi to create automated workflows without building a custom API integration. Zapier allows you to trigger Kisi actions (like creating users, generating access links, or unlocking doors) based on events in your system, or trigger actions in your system based on Kisi events. For example, when a new member signs up in your platform, you can automatically create a Kisi user and grant them access to specific doors. If your platform doesn't have Zapier integration yet, you can build one following Zapier's integration development guide. This approach is best suited for platforms that want to offer Kisi connectivity to their customers with low implementation effort using pre-built components rather than writing custom code.
If you need Kisi triggers or actions that are available in our API but not yet on Zapier, contact our support team to suggest additions to the Zapier integration.
For detailed information about available triggers and actions, see triggers and actions reference. For setup instructions, see set up Zapier automation.
Choosing the right integration method
Consider these factors when selecting your integration approach:
Marketplace listing: Any integration can apply for marketplace listing. Once approved, your integration will appear in the Kisi web dashboard where customers can discover and configure it. Apply here.