Load Flix data to DuckDB

Flix is a story development hub from Foundry that provides a RESTful HTTP API for managing data creation and retrieval between the Flix Client and Flix Server. Everything needed to build a working Flix → 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 Flix 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 Flix 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 Flix 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.

---

Flix API at a glance

These values come from the Flix API documentation. Check them against the vendor's current reference before relying on them in production.

---

How do I authenticate with the Flix API?

Flix server APIs typically require an access key (obtained via authentication endpoints) or a Bearer token in the 'Authorization' header. Specifically, the client API expects 'Authorization: BEARER ' in the request headers.

1. Get your credentials

To obtain API credentials for Flix, open the Flix Client application. Navigate to File > Management Console > API Keys. Within this menu, click the New API Key button. Enter a name for the key and select an expiration period. Upon clicking Create, the system will generate an ID and a Secret Key; you must copy and save the Secret Key immediately, as it cannot be retrieved again after the window is closed.

2. Add them to .dlt/secrets.toml

Copy
[sources.flix_source]
api_key = "your_secret_key_here"
# or if using a bearer token approach
# access_token = "your_token_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 Flix data can I load into DuckDB?

These are the Flix endpoints dlt can load into DuckDB:

---

How do I load only new Flix records?

Flix exposes page on queue_list, 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": "queue_items", "endpoint": {
    "path": "queue_list",
    "data_selector": "items",
    "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 Flix pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading info and status from the Flix API into DuckDB:

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

@dlt.source
def flix_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "http://localhost:8080 (Flix Server) or http://localhost:3000 (Flix Client)",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "queue_items", "endpoint": {"path": "queue_list", "data_selector": "items"}}
        ],
    }
    yield from rest_api_resources(config)


def load_flix_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="flix_pipeline",
        destination="duckdb",
        dataset_name="flix_data",
    )
    load_info = pipeline.run(flix_source())
    print(load_info)


if __name__ == "__main__":
    load_flix_to_duckdb()

Run it with python flix_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 Flix 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("flix_pipeline").dataset()
df = data.users.df()
print(df.head())

SQL:

Copy
SELECT * FROM flix_data.users LIMIT 10;

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

---

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