Gable is a fully integrated solution for seamless hybrid, remote, and in-office management. Our centralized platform means that Real estate, Workplace and People teams can effectively manage their employees whether they are in-office, hybrid or remote. By integrating with Verkada Admins can view all employees who are badging in for data, tracking and health and safety.

Time to complete: 15min

1. To access this integration you will first need to have Admin access to Gable. The Gable Company Admin can grant you these permissions by going to "Company Users" and updating your role.

2. Once enabled, log in and navigate to the dropdown in the top right hand corner. Select "Company Admin" and "Settings".

3. Select "Integrations"

4. Scroll to the bottom to the "Verkada" integration and "Connect".

5. Expand and follow the tooltip "How to create an API Key and set Expiration Date?" Log into Verkada and follow the step by step guide for creating the API, as follows:

5. Once you have generated the API Key, copy and paste it here in Gable along with the expiration date:

To find what region your organization was created in you'd expand this section

To show the following

The covered service regions can be found at this link below in the Verkada API article

https://apidocs.verkada.com/reference/service-regions

Once you've identified this and have your initial set up done you can move to the next step.

6. Scroll down to the "Webhook URL" and "Shared Secret in Verkada". Expand the tooltip, log into Verkada and complete the following steps:

7. Copy and paste the Webhook URL and Shared Secret from Gable into Verkada and hit "Save".

8.You will be taken to the second page of the integration where you have the option to connect a slack channel for Errors.

*Note: this needs to be a private channel, ensuring private user data doesn’t end up showing in public channels. You’ll need to create the channel and invite the Gable app for it to show up in the dropdown.

9. You can then map your Gable HQs (pre-loaded offices with floorplans) to your Verkada sites.

10. "Save" and your integration is complete.

Verkada’s API follows a two-factor authentication approach through the use of two different key types: a top-level API Key and a short-lived API Token. API Keys are created by Verkada Org Admins directly from within their Command Admin settings. Each API Key can have a unique permission set, broken down by Product and “Critical Endpoints”. Critical Endpoints are defined as high-vulnerability endpoints that allow critical control of Verkada devices, such as the Streaming API and Camera Audio API.

Using the top-level API Keys, users are able to generate short-lived API Tokens, valid for 30 minutes, that are required in order to authenticate at the endpoint level. It is important to store API Keys and API Tokens in a secure location, similar to your username and password. If a malicious user were to gain access to your API Key and API Tokens, they would gain a high-level of access to the creation or deletion of certain entities in your organization (ex. profiles of interest, access users, etc..).

Only organization admins have the ability to create API Keys (maximum of 10 API Keys per organization). Without Organization Admin permissions, users will not have access to the Verkada API page in Command. Upon creating an API Key, org admins will have the option to select between two different permission sets for each product line.

All changes to an API Key or a Webhook config are audit logged.

Still Have Questions? Please reach out to us at support@gable.to
​