Wandisco Live Data Migrator Python API Docs | dltHub

Build a Wandisco Live Data Migrator-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Wandisco Live Data Migrator is a REST API for managing data migration tasks and filesystem targets. The REST API base URL is http://<ldm-hostname>:18080 and All requests require either Basic Authentication (username/password) or a Bearer JWT token..

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 Wandisco Live Data Migrator data in under 10 minutes.


What data can I load from Wandisco Live Data Migrator?

Here are some of the endpoints you can load from Wandisco Live Data Migrator:

ResourceEndpointMethodData selectorDescription
stats/statsGETRetrieves basic statistics about the LDM instance.
fs_targets/fs/targetsGETLists filesystem targets configured in LDM.
jobs/jobsGETReturns migration jobs information.
tasks/tasksGETProvides details of individual migration tasks.
authentication/authentication/authenticatePOSTGenerates a JWT for Bearer authentication.

How do I authenticate with the Wandisco Live Data Migrator API?

Use HTTP Basic authentication by providing username and password (e.g., curl -u user:pass). Alternatively, POST to /authentication/authenticate with JSON {"userName":"...","password":"..."} to receive a JWT, then include it as 'Authorization: Bearer ' in subsequent calls.

1. Get your credentials

Contact your Wandisco Live Data Migrator administrator to obtain a username and password for Basic auth, or to receive a JWT generation endpoint token. No self‑service dashboard is described in the public docs.

2. Add them to .dlt/secrets.toml

[sources.wandisco_live_data_migrator_source] bearer_token = "your_jwt_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 Wandisco Live Data Migrator 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 wandisco_live_data_migrator_pipeline.py

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

Pipeline wandisco_live_data_migrator_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset wandisco_live_data_migrator_data The duckdb destination used duckdb:/wandisco_live_data_migrator.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline wandisco_live_data_migrator_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 stats and fs_targets from the Wandisco Live Data Migrator 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 wandisco_live_data_migrator_source(bearer_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://<ldm-hostname>:18080", "auth": { "type": "bearer", "token": bearer_token, }, }, "resources": [ {"name": "stats", "endpoint": {"path": "stats"}}, {"name": "fs_targets", "endpoint": {"path": "fs/targets"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="wandisco_live_data_migrator_pipeline", destination="duckdb", dataset_name="wandisco_live_data_migrator_data", ) load_info = pipeline.run(wandisco_live_data_migrator_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("wandisco_live_data_migrator_pipeline").dataset() sessions_df = data.stats.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM wandisco_live_data_migrator_data.stats LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("wandisco_live_data_migrator_pipeline").dataset() data.stats.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 Wandisco Live Data Migrator 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.


Troubleshooting

Authentication failures

  • If credentials are missing or incorrect, the API returns HTTP 401 Unauthorized. Verify that the username/password or JWT token is valid and that the Authorization header is correctly formatted.

Rate limiting

  • The API may limit request rates and respond with HTTP 429 Too Many Requests. Implement retry logic with exponential backoff when this status is received.

Pagination

  • List endpoints can return large collections. When a response includes a nextPageToken (or similar) field, use its value as a query parameter on the next request to retrieve subsequent pages. The exact pagination scheme is documented in the runtime Swagger UI.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


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 Wandisco Live Data Migrator?

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