Dagster Python API Docs | dltHub

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

Last updated:

The REST API base URL is Default local webserver: http://localhost:3000 (replace with your Dagster webserver host). For Dagster+ use https://{ORGANIZATION}.dagster.plus/{DEPLOYMENT_NAME} or https://{ORGANIZATION}.dagster.cloud/{DEPLOYMENT_NAME}. and all Dagster+ requests require an API token sent in the Dagster-Cloud-Api-Token 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 Dagster data in under 10 minutes.


What data can I load from Dagster?

Here are some of the endpoints you can load from Dagster:

ResourceEndpointMethodData selectorDescription
external_assets_report_materialization/report_asset_materialization/POSTRecord an AssetMaterialization event for an external asset
external_assets_report_check/report_asset_check/POSTRecord an AssetCheckEvaluation event for an external asset
external_assets_report_observation/report_asset_observation/POSTRecord an AssetObservation event for an external asset
(Notes: official docs primarily document these REST endpoints which are POST-only; the API returns JSON for success ({} on 200) and error responses contain an "error" object.)

How do I authenticate with the Dagster API?

Dagster+ requires a user token sent in the Dagster-Cloud-Api-Token request header. Open-source/local deployments typically do not require this header (use host auth/proxy as configured).

1. Get your credentials

  1. Sign in to Dagster Cloud (or Dagster+) as an organization user.
  2. Navigate to the deployment or user token settings in the web UI.
  3. Create/generate a user API token and copy it. Use that token as the value for Dagster-Cloud-Api-Token in request headers or in secrets.toml.

2. Add them to .dlt/secrets.toml

[sources.dagster_source] # place inside [sources.dagster_source] dagster_cloud_api_token = "your_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 Dagster 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 dagster_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline dagster_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 external_assets_report_materialization and external_assets_report_check from the Dagster 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 dagster_source(dagster_cloud_api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "Default local webserver: http://localhost:3000 (replace with your Dagster webserver host). For Dagster+ use https://{ORGANIZATION}.dagster.plus/{DEPLOYMENT_NAME} or https://{ORGANIZATION}.dagster.cloud/{DEPLOYMENT_NAME}.", "auth": { "type": "api_key", "Dagster-Cloud-Api-Token": dagster_cloud_api_token, }, }, "resources": [ {"name": "external_assets_report_materialization", "endpoint": {"path": "report_asset_materialization/"}}, {"name": "external_assets_report_check", "endpoint": {"path": "report_asset_check/"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="dagster_pipeline", destination="duckdb", dataset_name="dagster_data", ) load_info = pipeline.run(dagster_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("dagster_pipeline").dataset() sessions_df = data.external_assets_report_materialization.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM dagster_data.external_assets_report_materialization LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("dagster_pipeline").dataset() data.external_assets_report_materialization.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 Dagster 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 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 Dagster?

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