Verkada Python API Docs | dltHub
Build a Verkada-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Verkada Command API provides programmatic access to manage Verkada devices and extract data from the Command platform. The REST API base URL is https://api.verkada.com and all requests require an x-verkada-auth header containing a short-lived token obtained via an API key.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Verkada data in under 10 minutes.
What data can I load from Verkada?
Here are some of the endpoints you can load from Verkada:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| access_events | access/v1/events | GET | events | Retrieve access events with pagination |
| lpr_zones | v2/cameras/lpr/zones | GET | items | List all LPR zones |
| lpr_zone_records | v2/cameras/lpr/zones/{zone_id}/records | GET | records | List records for a specific LPR zone |
| alerts | cameras/v1/alerts | GET | alerts | List camera alerts |
| camera_info | camera/v1/info | GET | cameras | List camera information |
How do I authenticate with the Verkada API?
Verkada uses a two-tier authentication model. Users must first call the /token endpoint with their 'x-api-key' header to retrieve a short-lived API token, which is then passed as an 'x-verkada-auth' header in subsequent API requests.
1. Get your credentials
To obtain credentials for the Verkada REST API, you must be an Organization Admin in the Verkada Command platform. Follow these steps: 1. Log in to Verkada Command and navigate to the Admin page. 2. Open Organization Settings and select the Verkada API tab. 3. Click the '+ New API Key' button. 4. Provide a name for the key and define the required permission scope (Product and 'Critical Endpoints'). 5. Set the desired key expiration and click 'Generate Key'. 6. Copy the displayed API Key immediately, as it will not be shown again. 7. Use this API Key to authenticate and request a short-lived (30-minute) API Token via the /token endpoint, which is required for making requests to most API endpoints.
2. Add them to .dlt/secrets.toml
[sources.verkada_source] api_key = "REPLACE_ME"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Verkada API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python verkada_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline verkada_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset verkada_data The duckdb destination used duckdb:/verkada.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads /token (for obtaining short-lived authentication tokens) and /[resource-path] (e.g., specific camera or event endpoints) from the Verkada API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def verkada_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.verkada.com", "auth": {"type": "api_key", "api_key": api_key, "name": "x-verkada-auth", "location": "header"}, }, "resources": [ {"name": "lpr_zones", "endpoint": {"path": "v2/cameras/lpr/zones", "data_selector": "items"}}, {"name": "lpr_zone_records", "endpoint": {"path": "v2/cameras/lpr/zones/{zone_id}/records", "data_selector": "records"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="verkada_pipeline", destination="duckdb", dataset_name="verkada_data", ) load_info = pipeline.run(verkada_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("verkada_pipeline").dataset() sessions_df = data.lpr_zone_records.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM verkada_data.lpr_zone_records LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("verkada_pipeline").dataset() data.lpr_zone_records.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Verkada data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Verkada?
Request dlt skills, commands, AGENT.md files, and AI-native context.