Load Redox data to DuckDB

Redox is an interoperability platform that provides APIs for exchanging healthcare data and managing organization configurations. Everything needed to build a working Redox → 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 Redox 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 Redox 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 Redox 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.

---

Redox API at a glance

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

---

How do I authenticate with the Redox API?

The Redox API uses OAuth 2.0 Bearer authentication. Requests must include an Authorization header with the format 'Authorization: Bearer {access_token}', where the access token is obtained via an authentication request.

1. Get your credentials

1. Log in to the Redox dashboard. 2. Navigate to the Developer page in the main menu. 3. Ensure the Sources tab is active (default). 4. Click the 'New OAuth API key' button to create a new key, or click 'Edit' next to an existing one. 5. In the API key details modal, provide a name for the key. 6. Once created, the Settings page will display the 'Client ID'. 7. Choose to either generate a new private/public key pair within the dashboard or provide your own public key. 8. Store the resulting Client ID and private key securely.

2. Add them to .dlt/secrets.toml

Copy
[sources.redox_source]
redox_client_id = "YOUR_CLIENT_ID"
redox_private_key = "-----BEGIN RSA PRIVATE KEY-----\n...\n-----END RSA PRIVATE KEY-----"

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 Redox data can I load into DuckDB?

These are the Redox endpoints dlt can load into DuckDB:

---

How do I load only new Redox records?

Redox exposes createdAfter on platform/organizations, 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": "organizations", "endpoint": {
    "path": "platform/organizations",
    "data_selector": "payload.records",
    "incremental": {"cursor_path": "createdAfter", "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 Redox pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading https://api.redoxengine.com/v2/auth/token and https://api.redoxengine.com/platform/{endpoint} from the Redox API into DuckDB:

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

@dlt.source
def redox_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.redoxengine.com",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "organizations", "endpoint": {"path": "platform/organizations", "data_selector": "payload.records"}},
            {"name": "sources", "endpoint": {"path": "platform/sources", "data_selector": "payload.records"}}
        ],
    }
    yield from rest_api_resources(config)


def load_redox_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="redox_pipeline",
        destination="duckdb",
        dataset_name="redox_data",
    )
    load_info = pipeline.run(redox_source())
    print(load_info)


if __name__ == "__main__":
    load_redox_to_duckdb()

Run it with python redox_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 Redox 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("redox_pipeline").dataset()
df = data.logs.df()
print(df.head())

SQL:

Copy
SELECT * FROM redox_data.logs LIMIT 10;

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

---

How do I deploy the Redox 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 Redox 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 Redox 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