canonical: https://jentic.com/apis/verkada.com/verkada

# Verkada API

Verkada security platform API for managing cameras, access control, sensors, and guest management. The API exposes 9 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get API token, get camera alerts. Covers 9 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for security only.

## Capabilities

- Get API token
- Unlock a door
- Create a user
- Query and filter Verkada API records by parameters
- Monitor Verkada API operational status and events

## Use cases

### Security Operations

Use the Verkada API to perform security operations programmatically. The API provides 9 endpoints covering core functionality including get API token, get camera alerts, get camera information.

Example prompt: Call POST `/login/api-key/view/v2` to get API token

### Automated Access Management

Automate access operations by combining multiple Verkada API endpoints. Agents can get camera alerts and then get camera information in a single workflow.

Example prompt: Call GET `/notifications/view/v1` to get camera alerts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Verkada API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get API token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/login/api-key/view/v2` | Get API token |
| GET | `/notifications/view/v1` | Get camera alerts |
| GET | `/camera/info/view/v1` | Get camera information |
| GET | `/access/groups/view/v1` | Get all access groups |
| POST | `/access/admin-api/unlock/view/v1` | Unlock a door |
| GET | `/audit-logs/view/v1` | Get audit logs |
| POST | `/user/view/v1` | Create a user |
| GET | `/sensor/alerts/view/v1` | Get sensor alerts |

## Key resources

- **Access** — Operations for access
- **Audit Logs** — Operations for audit logs
- **Camera** — Operations for camera
- **Guest** — Operations for guest
- **Login** — Operations for login

## Why Jentic

- **Setup:** Wiring the Verkada API by hand means exchanging your x-api-key for the x-verkada-auth token against api.verkada.com and coding each camera, access, and sensor operation yourself. Through Jentic you install once, import the Verkada API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Verkada operations carry their door and device targets in the request body and query rather than a single path id, so limit the agent to the operations it needs, such as viewing camera info or reading audit logs. You choose that allowed set, so actions like unlocking a door are excluded unless you add them.
- **Credential handling:** Your Verkada API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get camera info' or 'read access audit logs', and Jentic returns the matching Verkada operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Snyk** — Alternative security API
- **Crowdstrike** — Alternative security API

## FAQ

### What authentication does the Verkada API use?

The Verkada API uses an API key passed in the `x-api-key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get API token with the Verkada API?

Yes. Use the POST `/login/api-key/view/v2` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Verkada API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get API token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get API token'. Jentic returns the matching Verkada API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Verkada API have?

The Verkada API exposes 9 endpoints covering access, audit logs, camera operations.

### Can I limit what my agent is allowed to do with the Verkada API?

Yes. Because you self-host Jentic One, your own rules decide which Verkada operations and credentials the agent may use, so you can allow read-only calls like getting camera information (GET `/camera/info/view/v1`) or reading audit logs (GET `/audit-logs/view/v1`) while withholding everything else. Verkada carries its door and device targets in the request body and query rather than a single path id, so you scope by whole operations rather than by target. Write actions such as unlocking a door (POST `/access/admin-api/unlock/view/v1`) or creating a user stay excluded unless you add them to the allowed set.