Scenarios
In the API, lockdowns are represented as scenarios. Each scenario includes a type field that defines its purpose. You can programmatically manage Verkada scenarios, such as listing available lockdowns, activating one, or releasing an active one, using third-party platforms and automation tools.
Command configuration
Organization level
In Verkada Command, go to All Products > Access
.On the left navigation, click
Access Settings.Toggle on Enable Lockdown and Scenario Control via API.
Generate API key
In Verkada Command, go to All Products >
Admin.Under Org Settings, click API & Integrations.
From the API & Integration settings, select API Keys > Add.
Select New Key and click Next.
Enter a unique name.
Under Endpoints, select Access Control.
Set the permissions to Read/Write.
Set the expiration date.
Click Generate API.
Available API actions
Once you configure Command to allow API control of scenarios, you can perform the following actions:
List Scenarios: Retrieve all configured scenarios across your organization.
Activate a Scenario: Trigger a scenario programmatically in response to an event or condition.
Release a Scenario: End or deactivate an active scenario.
See Verkada API Docs for more details on specific Access Control API endpoints.
Activate and release a scenario via API
When a scenario such as a lockdown is activated or released through the API, it behaves the same as if it were triggered manually in Command.
Using the API to activate or release a scenario will:
Execute all configured scenario actions, such as locking doors, triggering alerts, or activating AUX outputs.
Update the scenario’s status in both the Command interface and the Verkada Pass app.
Generate event logs for each action, visible in the Events report and the Command audit log.
Need more help? Contact Verkada Support.