Load Exact data to DuckDB

100ms is a video and audio infrastructure platform that provides REST APIs to manage rooms, sessions, templates, and other real-time media resources. Everything needed to build a working Exact → 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 Exact 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 Exact 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 Exact 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.

---

Exact API at a glance

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

---

How do I authenticate with the Exact API?

Requests must include an 'Authorization' header with a 'Bearer <management_token>' value and a 'Content-Type' header set to 'application/json'.

1. Get your credentials

To obtain API credentials for use with dlt, you must navigate to the developer portal or account settings dashboard of the specific third-party REST API service you are integrating. Once generated, these credentials (e.g., API keys, tokens, client IDs) should be stored securely on your local system using the dlt credentials mechanism rather than hardcoded into your scripts. The standard practice for local development is to use a .dlt/secrets.toml file, which is created during the dlt project initialization command (dlt init ). Place your sensitive credentials within this file under a section corresponding to your source configuration. For production environments, consider using environment variables (e.g., SOURCES<KEY_NAME>) or supported secret management services like Google Secret Manager, AWS Secrets Manager, or Azure Key Vault.

2. Add them to .dlt/secrets.toml

Copy
[sources.exact_source]
api_key = "your_actual_api_key_here"

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

These are the Exact endpoints dlt can load into DuckDB:

---

How do I load only new Exact records?

Exact exposes updated_at on users, 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": "users", "endpoint": {
    "path": "users",
    "data_selector": "results",
    "incremental": {"cursor_path": "updated_at", "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 Exact pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading client and resources from the Exact API into DuckDB:

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

@dlt.source
def exact_source(management_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.100ms.live/v2",
            "auth": {"type": "bearer", "token": management_token},
        },
        "resources": [
            {"name": "users", "endpoint": {"path": "users", "data_selector": "results"}},
            {"name": "posts", "endpoint": {"path": "posts", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


def load_exact_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="exact_pipeline",
        destination="duckdb",
        dataset_name="exact_data",
    )
    load_info = pipeline.run(exact_source())
    print(load_info)


if __name__ == "__main__":
    load_exact_to_duckdb()

Run it with python exact_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 Exact 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("exact_pipeline").dataset()
df = data.users.df()
print(df.head())

SQL:

Copy
SELECT * FROM exact_data.users LIMIT 10;

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

---

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