Veeam Backup and Replication Python API Docs | dltHub
Build a Veeam Backup and Replication-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Veeam Backup & Replication REST API uses HTTPS and REST principles for operations; MFA is supported for enhanced security; access tokens are required for authorization. The REST API base URL is https://<hostname>:9419/api and All requests require a Bearer token passed 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 pip install "dlt[workspace]" and start loading Veeam Backup and Replication data in under 10 minutes.
What data can I load from Veeam Backup and Replication?
Here are some of the endpoints you can load from Veeam Backup and Replication:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| sessions | /api/v1/sessions | GET | sessions | List all backup sessions |
| jobs | /api/v1/jobs | GET | jobs | List backup jobs and their status |
| backups | /api/v1/backups | GET | backups | List backup objects (restore points) |
| repositories | /api/v1/repositories | GET | repositories | List storage repositories used by Veeam |
| agents | /api/v1/agents | GET | agents | List protected agents/endpoints |
How do I authenticate with the Veeam Backup and Replication API?
Obtain an access token via POST /api/oauth2/token (include x-api-version header) and include it as 'Authorization: Bearer <access_token>' on every request.
1. Get your credentials
- Prepare your client credentials (e.g., username and password or client ID/secret).
- Send an HTTP POST to https://:9419/api/oauth2/token.
- Include the header
x-api-version: 1.3-rev1. - In the request body, supply the required grant_type and credential fields as defined by the API (typically
grant_type=password,username,password). - The response contains
access_tokenandrefresh_token; store theaccess_tokenfor use in subsequent calls.
2. Add them to .dlt/secrets.toml
[sources.veeam_backup_and_replication_source] access_token = "your_access_token_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 Veeam Backup and Replication 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 veeam_backup_and_replication_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline veeam_backup_and_replication_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset veeam_backup_and_replication_data The duckdb destination used duckdb:/veeam_backup_and_replication.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline veeam_backup_and_replication_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 sessions and jobs from the Veeam Backup and Replication 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 veeam_backup_and_replication_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<hostname>:9419/api", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "sessions", "endpoint": {"path": "v1/sessions", "data_selector": "sessions"}}, {"name": "jobs", "endpoint": {"path": "v1/jobs", "data_selector": "jobs"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="veeam_backup_and_replication_pipeline", destination="duckdb", dataset_name="veeam_backup_and_replication_data", ) load_info = pipeline.run(veeam_backup_and_replication_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("veeam_backup_and_replication_pipeline").dataset() sessions_df = data.sessions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM veeam_backup_and_replication_data.sessions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("veeam_backup_and_replication_pipeline").dataset() data.sessions.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 Veeam Backup and Replication 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 Veeam Backup and Replication?
Request dlt skills, commands, AGENT.md files, and AI-native context.