Dask Python API Docs | dltHub
Build a Dask-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Dask provides an HTTP interface on its scheduler for monitoring cluster state and performing administrative tasks like managing workers. The REST API base URL is https://<scheduler-host>:8787 and authentication is deployment-dependent, often requiring an API key passed as a Bearer token in the 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 Dask data in under 10 minutes.
What data can I load from Dask?
Here are some of the endpoints you can load from Dask:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| sitemap | sitemap.json | GET | List available endpoints on the scheduler HTTP server | |
| workers | api/v1/get_workers | GET | Get all workers on the scheduler | |
| identity | json/identity.json | GET | Scheduler identity and info | |
| counts | json/counts.json | GET | Cluster counts and stats | |
| health | health | GET | Health check for scheduler/worker HTTP service | |
| metrics | metrics | GET | Prometheus metrics endpoint | |
| adaptive_target | api/v1/adaptive_target | GET | Get adaptive target number of workers | |
| retire_workers | api/v1/retire_workers | POST | Retire certain workers on the scheduler |
How do I authenticate with the Dask API?
Authentication is deployment-dependent, as core Dask components do not include built-in HTTP authentication by default. When enabled (via distributed.scheduler.http.api-key), requests must include the key in the Authorization header using the format Bearer {api-key}.
1. Get your credentials
The core Dask scheduler HTTP API does not provide a built-in credential issuance dashboard. Authentication is deployment-dependent. 1. If using a managed Dask service or Dask Gateway, log in to the provider's specific dashboard to retrieve your API token or credentials, or use the provider's CLI (e.g., dask gateway token list). 2. For custom or self-hosted deployments, an API key is typically generated by the infrastructure administrator and must be defined in the cluster's configuration file under distributed.scheduler.http.api-key. Retrieve this key directly from that configuration or deployment setting.
2. Add them to .dlt/secrets.toml
[sources.dask_source] api_key = "your_generated_api_key_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 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 Dask 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 dask_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline dask_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset dask_data The duckdb destination used duckdb:/dask.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/v1/get_workers and /json/identity.json from the Dask 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 dask_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<scheduler-host>:8787", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "workers", "endpoint": {"path": "api/v1/get_workers"}}, {"name": "sitemap", "endpoint": {"path": "sitemap.json"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="dask_pipeline", destination="duckdb", dataset_name="dask_data", ) load_info = pipeline.run(dask_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("dask_pipeline").dataset() sessions_df = data.workers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM dask_data.workers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("dask_pipeline").dataset() data.workers.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 Dask 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 Dask?
Request dlt skills, commands, AGENT.md files, and AI-native context.