This article explains how to integrate Suprema BioStation 3 biometric readers with Verkada’s access control system. It covers customer-provided information and Suprema’s configuration, with Verkada supplying the access control infrastructure and cloud management tools, and Suprema handling facial recognition and biometric data.
Integration overview
All users and access levels are managed in Verkada Command. Suprema uses Verkada’s APIs to retrieve user data and profile photos, then generates a unique credential string for each face and uploads it to Command. When a user attempts entry, the BioStation 3 scans their face, converts it into the credential string, and sends it to Verkada’s ACU. If the credentials match, access is granted.
Suprema lets users set a custom sync cycle to regularly pull the latest Command user data and keep permissions current. For details on facial enrollment and best practices, see Suprema’s knowledge base article.
To deploy this integration, you will create an API token and provide it to Suprema. The token grants access to retrieve data and make changes in Command, and customers are responsible for keeping it secure. Verkada is not liable for any data accessed or modifications made in Command using a customer’s API token.
System requirements
| Hardware | Software |
Verkada |
|
|
Suprema |
|
|
Required API credentials
Verkada API Key Configuration
Users will need to create a Verkada API key with the following properties:
Name - Any descriptive name (e.g., "Suprema Integration Key").
Endpoint Access
Core Command - Can be Read/Write or Read-Only.
Access Control - Must be Read/Write to enable user provisioning and access level assignment.
Expiration - Set according to your organization's security policy.
Region Setting - Navigate to Command > Privacy & Security > Data Residency to confirm the correct region (e.g., US, EU).
Suprema API Credential
CLUe Place API Key - Provided by Suprema as part of the DataXfer setup.
When you use an API key or allow others to use it, you are responsible for ensuring all activity complies with the API Use Policy. Verkada is not liable for any data once it leaves the Command platform.
Suprema configuration
Step 1: Provide Verkada information to Suprema
Users must provide the following Verkada details to Suprema’s integration team:
A valid API key from your Verkada Command account (see required API credentials).
The region setting for your Verkada instance (e.g., US, EU).
The Command access level in Verkada to be used for user synchronization. Suprema will map user profiles to this access level.
Step 2: Suprema Configuration — CLUe Setup
Once the required information is received, Suprema will configure the CLUe platform.
Suprema responsibilities for CLUe:
Create CLUe Place and Site - Suprema will provision a dedicated “Place” and “Site” for the customer within the CLUe platform.
Add BS3 Devices - Suprema will register and associate all BioStation 3 (BS3) units to the CLUe Site.
Create CLUe API - API integration point will be created to connect the CLUe platform with Verkada, enabling user data transfer and management.
Step 3: Suprema Configuration — DataXfer Setup
Once the CLUe platform is configured, Suprema will set up and validate data transfer using the DataXfer tool.
Suprema Responsibilities for DataXfer:
Create DataXfer Site - A dedicated DataXfer site will be provisioned to sync data between CLUe and Verkada.
Test User Data Transfer - Suprema will perform a test transfer to ensure user profiles correctly move from the Suprema system into Verkada Command.
Step 4: Hardware installation and wiring
The final step involves physical installation and wiring by the customer or on-site technician.
Customer Responsibilities:
Wire BS3 Device to Verkada Access Control Panel - Connect the BioStation 3 Wiegand output to the correct input on the Verkada panel.
Verify Signal Communication - Confirm that Wiegand signals from the BS3 are correctly processed by Verkada, ensuring badge reads or biometric scans trigger access events.
Need help? Contact Verkada Support.