OPNsense Python API Docs | dltHub
Build a OPNsense-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
OPNsense REST API documentation is available at https://docs.opnsense.org/development/api.html. It uses key/secret pairs for authentication and supports GET and POST methods. API calls can be tested using tools like Postman or cURL. The REST API base URL is https://<your_opnsense_ip_or_hostname>/api and All requests require a key and secret pair for HTTP Basic Authentication..
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 pip install "dlt[workspace]" and start loading OPNsense data in under 10 minutes.
What data can I load from OPNsense?
Here are some of the endpoints you can load from OPNsense:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| core_firmware_status | core/firmware/status | GET | Get firmware status | |
| core_firmware_upgrade | core/firmware/upgrade | POST | Upgrade firmware | |
| core_service_search | core/service/search | POST | rows | Search services |
| diagnostics_interface_get_interface_stats | diagnostics/interface/getInterfaceStats | GET | Get interface statistics | |
| firewall_alias_get | firewall/alias/get | GET | Get firewall aliases | |
| system_log_core_get | system/log/core/get | GET | Get core system logs |
How do I authenticate with the OPNsense API?
Authentication for the OPNsense API uses key/secret pairs via HTTP Basic Authentication. The key acts as the username and the secret as the password.
1. Get your credentials
- Log in to your OPNsense instance's web interface.
- Navigate to System -> Access -> Users.
- Create a new user or select an existing user.
- Ensure the user has the necessary permissions for API access.
- Go to System -> Access -> API Keys.
- Generate a new API key. You will receive a key/secret pair, typically in an INI-formatted text file, which you should download and store securely. The 'key' acts as the username and the 'secret' as the password for API authentication.
2. Add them to .dlt/secrets.toml
[sources.opnsense_source] api_key = "your_api_key_here" api_secret = "your_api_secret_here"
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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt 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:
dlt ai toolkit rest-api-pipeline install
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 OPNsense 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:
python opnsense_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline opnsense_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset opnsense_data The duckdb destination used duckdb:/opnsense.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline opnsense_pipeline 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 core_firmware_status and core_service_search from the OPNsense 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 opnsense_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<your_opnsense_ip_or_hostname>/api", "auth": { "type": "http_basic", "username": api_key, }, }, "resources": [ {"name": "core_firmware_status", "endpoint": {"path": "core/firmware/status"}}, {"name": "core_service_search", "endpoint": {"path": "core/service/search", "data_selector": "rows"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="opnsense_pipeline", destination="duckdb", dataset_name="opnsense_data", ) load_info = pipeline.run(opnsense_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("opnsense_pipeline").dataset() sessions_df = data.core_firmware_status.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM opnsense_data.core_firmware_status LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("opnsense_pipeline").dataset() data.core_firmware_status.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 OPNsense 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 Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for OPNsense?
Request dlt skills, commands, AGENT.md files, and AI-native context.