Broadcom VMware Live Cyber Recovery Python API Docs | dltHub

Build a Broadcom VMware Live Cyber Recovery-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

VMware Live Cyber Recovery is a REST API providing access to cloud file systems, protected sites, VMs, protection groups, and recovery plans for ransomware and disaster recovery operations. The REST API base URL is https://{instance}.app.vcdr.vmware.com/api/vcdr/v1 and all requests require an access token passed in a 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 Broadcom VMware Live Cyber Recovery data in under 10 minutes.


What data can I load from Broadcom VMware Live Cyber Recovery?

Here are some of the endpoints you can load from Broadcom VMware Live Cyber Recovery:

ResourceEndpointMethodData selectorDescription
cloud_file_systemscloud-file-systemsGETcloud_file_systemsList Cloud File Systems
protected_sitesprotected-sitesGETprotected_sitesList Protected Sites
protected_vmscloud-file-systems/{cloud_file_system_id}/protected-vmsGETvmsList Protected Virtual Machines
protection_groupscloud-file-systems/{cloud_file_system_id}/protection-groupsGETprotection_groupsList Protection Groups
protection_group_snapshotscloud-file-systems/{cloud_file_system_id}/protection-groups/{protection_group_id}/snapshotsGETsnapshotsList Snapshots for a Protection Group
recovery_planscloud-file-systems/{cloud_file_system_id}/recovery-plansGETrecovery_plansList Recovery Plans
recovery_sddcsrecovery-sddcsGETrecovery_sddcsList Recovery SDDCs

How do I authenticate with the Broadcom VMware Live Cyber Recovery API?

Authentication requires a Bearer token, which must be passed in the x-da-access-token header for all REST API calls. You must first exchange a VMware Cloud Services Platform (CSP) API Token for an access token via the authentication endpoint.

1. Get your credentials

To obtain credentials for the VMware Live Cyber Recovery API, you must create a Server-to-Server OAuth 2.0 app within the Broadcom Cloud Console. 1. Log in to the Broadcom Cloud Console. 2. Navigate to the OAuth Apps section in the side navigation. 3. Click 'Create New OAuth App' and select 'Server to Server' app. 4. Configure the app with appropriate permissions (e.g., Global Console Admin, Orchestrator Admin) and select the 'VMware Live Recovery' service. 5. Upon creation, copy the generated App ID and App Secret. You will use these to programmatically obtain an access token. Note that for standard service interactions, these tokens are exchanged via the Cloud Services Platform (CSP) API.

2. Add them to .dlt/secrets.toml

[sources.broadcom_vmware_live_cyber_recovery_source] access_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 Broadcom VMware Live Cyber Recovery 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 broadcom_vmware_live_cyber_recovery_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline broadcom_vmware_live_cyber_recovery_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset broadcom_vmware_live_cyber_recovery_data The duckdb destination used duckdb:/broadcom_vmware_live_cyber_recovery.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 /api/vcdr/v1/cloud-file-systems and /api/vcdr/v1/cloud-file-systems/{cloud_file_system_id}/protected-vms-batch from the Broadcom VMware Live Cyber Recovery 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 broadcom_vmware_live_cyber_recovery_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{instance}.app.vcdr.vmware.com/api/vcdr/v1", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "protected_vms", "endpoint": {"path": "cloud-file-systems/{cloud_file_system_id}/protected-vms", "data_selector": "vms"}}, {"name": "recovery_plans", "endpoint": {"path": "cloud-file-systems/{cloud_file_system_id}/recovery-plans", "data_selector": "recovery_plans"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="broadcom_vmware_live_cyber_recovery_pipeline", destination="duckdb", dataset_name="broadcom_vmware_live_cyber_recovery_data", ) load_info = pipeline.run(broadcom_vmware_live_cyber_recovery_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("broadcom_vmware_live_cyber_recovery_pipeline").dataset() sessions_df = data.recovery_plans.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM broadcom_vmware_live_cyber_recovery_data.recovery_plans LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("broadcom_vmware_live_cyber_recovery_pipeline").dataset() data.recovery_plans.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 Broadcom VMware Live Cyber Recovery data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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 Broadcom VMware Live Cyber Recovery?

Request dlt skills, commands, AGENT.md files, and AI-native context.