Load Redash data to DuckDB

Redash is a collaborative data visualization and dashboarding platform that provides a REST API for managing queries, dashboards, and query results. Everything needed to build a working Redash → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Redash to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Redash to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Redash API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Redash API at a glance

These values come from the Redash API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Redash API?

Redash supports authentication via an API key. The key can be passed as a query parameter named 'api_key' or via an HTTP header 'Authorization: Key <api_key>'.

1. Get your credentials

To obtain an API key for Redash, log in to your Redash instance, click your profile icon in the top-right corner, and select Profile (or Account/Settings). Locate the API Key section on your profile page and click the button to show or copy your User API Key. For production data pipelines, ensure you are using an admin-level user key if you need access to multiple organizations or restricted data objects.

2. Add them to .dlt/secrets.toml

Copy
[sources.redash_source]
redash_api_key = "your_user_api_key_here"
redash_base_url = "https://your-redash-instance-url.com"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Redash data can I load into DuckDB?

These are the Redash endpoints dlt can load into DuckDB:

---

How do I load only new Redash records?

Redash exposes page on api/queries, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "queries", "endpoint": {
    "path": "api/queries",
    "data_selector": "queries",
    "incremental": {"cursor_path": "page", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Redash pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /api/queries and /api/dashboards from the Redash API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def redash_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "The base URL is the base URL of your Redash instance, with API endpoints appended (e.g., https://your-redash-instance.com/api).",
            "auth": {"type": "api_key", "api_key": api_key, "name": "Authorization", "location": "header"},
        },
        "resources": [
            {"name": "queries", "endpoint": {"path": "api/queries", "data_selector": "queries"}},
            {"name": "dashboards", "endpoint": {"path": "api/dashboards", "data_selector": "dashboards"}}
        ],
    }
    yield from rest_api_resources(config)


def load_redash_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="redash_pipeline",
        destination="duckdb",
        dataset_name="redash_data",
    )
    load_info = pipeline.run(redash_source())
    print(load_info)


if __name__ == "__main__":
    load_redash_to_duckdb()

Run it with python redash_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Redash data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("redash_pipeline").dataset()
df = data.queries.df()
print(df.head())

SQL:

Copy
SELECT * FROM redash_data.queries LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Redash to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Redash loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Redash data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack