Learn more about Kisi's open API.
How much time and money do you spend issuing and programming new ID cards and keys every year?
What if, for a fraction of the cost and time, you could replace nearly all your physical access credentials with secure digital ones that require only a smartphone to use?
Access-Control-as-a-Service (ACaaS) gives you more control over building management. As well as handling access control, it gives you real-time information on who is in your buildings, and you can integrate ACaaS platforms with other external sources of information in your organization such as CRM and calendars. This helps solve the problem of onboarding and offboarding staff, members, and visitors, as well as lost keys and security concerns.
Most smartphone-based ACaaS platforms share a few key attributes: Users typically download an app through which you assign permissions to them, and then they gain access through readers or sensors posted at entrances. This is similar to how a badge or contactless card works.
Most smart lock solutions on the market are not designed for multiple access points and don’t have the ability to grant different permissions for different locations depending on the type of access a staff member or visitor needs. With Kisi, you can handle this process with an administration or front desk member of staff.
Now, you may be thinking that just as people don’t carry keys all the time, they may not always carry—or even own—a smartphone. Kisi offers the ability to supply alternative credentials, including integration with swipe cards.
Let’s take a look at all of the available API options:
Learn more about Kisi's open API.
The main area of your Kisi dashboard shows the locations you’ve defined and allows you to click on the location to see the access points, users, groups, and settings for that location. For example, the “Kisi Demo” location in the screenshot below has two access points and 366 users in one group.
The Kisi Dashboard
The Settings pane of the dashboard provides access to analytics information and any integrations you’ve added.
To start, create an instance of the client, authenticate with the API, and list your places, use the following:
This code results in a JSON response of your places, with all the metadata associated with each place. To get the details of a particular lock, use the following with the ID of the place:
This code is equivalent to the below screen in the web dashboard:
Locks in a place
To unlock a lock, pass the lock ID:
If you don’t want to build a custom integration, Kisi includes integrations with a dozen services that provide your places, locks, and members with data from external sources. These include Active Directory and Google Apps for user lists, door management linked to calendar entries, member access levels from six different membership services, and connectivity to security video systems. You can add these integrations from the web app, as well as from the API by using our integrations resources.
Add a calendar connection to Kisi
Combining these integrations with your custom applications gives tremendous potential. For example, when a new client signs up with their Google account, your custom application checks that the user has a valid membership and if so, grants them access to your doors.
The power of the Kisi platform comes from its extensibility: An open API allows limitless possibilities for getting data in and out of the platform to trigger actions and create applications beyond pure access control.
“Kisi’s API documentation is so clear that we had our beta version up and running in 24 hours." Nigel Thomas, CEO at GoLocker
Take, for example, intrusion detection. You could use sensors connected to your Kisi controller and attached to external doors or windows. Then, with a custom application, use the integrations endpoint to add a new webhook listener:
When a sensor triggers that webhook, you can use the body set above to then trigger further Kisi or 3rd party API endpoints that match your use case, such as preventing the intruder from opening the door from the inside or triggering an alarm system.
Alternatively, take the example of using proximity sensors to introduce even more convenience to your building: By using a proximity sensor triggered by an authorized keycard or mobile device, you can use the unlock endpoint to open a lock as the person nears it and simultaneously record exit events for individuals and your building.
There are three use cases that we see most frequently for working with the Kisi API and integrating it with your application or infrastructure:
Thanks to the API, the potential use cases go further than these, and we look forward to hearing what you build. For inspiration, check out some advanced implementations from customers who leveraged the potential of our API.