Load Frigate data in Python using dltHub
Build a Frigate-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Frigate is a NVR software providing an HTTP API for managing cameras, events, and system configuration. The REST API base URL is http://<frigate_host>:<port>/api and API requests require a Bearer token in the Authorization header..
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 Frigate data in under 10 minutes.
What data can I load from Frigate?
Here are some of the endpoints you can load from Frigate:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| events | /events | GET | Returns a list of events | |
| events_search | /events/search | GET | Searches for events in the database | |
| events_summary | /events/summary | GET | Gets a summary of objects | |
| config | /config | GET | Returns the active configuration | |
| go2rtc_streams | /go2rtc/streams | GET | Gets list of go2rtc streams |
How do I authenticate with the Frigate API?
Authentication is performed by obtaining a JWT token via a POST request to the /api/login endpoint and including it in the Authorization header as a Bearer token. Subsequent requests require the 'Authorization: Bearer <token_value>' header.
1. Get your credentials
Frigate NVR does not use static API keys for authentication. Instead, it uses JWT-based sessions. To authenticate and obtain a token for API requests:\n\n1. Identify your Frigate instance URL and the port used for authenticated access (default: 8971).\n2. Authenticate by making a POST request to the /api/login endpoint with your admin username and password in the request body (e.g., {"user": "admin", "password": "your_password"}).\n3. The response will include a session cookie containing a JWT token. You can extract this token or use the cookie for subsequent requests. Alternatively, many users use this JWT token as a Bearer token in the Authorization header (Authorization: Bearer <your_token>).
2. Add them to .dlt/secrets.toml
[sources.frigate_source] api_token = "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 Frigate 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 frigate_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline frigate_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset frigate_data The duckdb destination used duckdb:/frigate.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 /login and /auth from the Frigate 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 frigate_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://<frigate_host>:<port>/api", "auth": {"type": "bearer", "token": api_token}, }, "resources": [ {"name": "events", "endpoint": {"path": "events"}}, {"name": "events_search", "endpoint": {"path": "events/search"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="frigate_pipeline", destination="duckdb", dataset_name="frigate_data", ) load_info = pipeline.run(frigate_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("frigate_pipeline").dataset() sessions_df = data.events.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM frigate_data.events LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("frigate_pipeline").dataset() data.events.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 Frigate 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 Frigate?
Request dlt skills, commands, AGENT.md files, and AI-native context.