Load Dailymotion data to DuckDB

Dailymotion API is a REST API that lets you read and manage Dailymotion content programmatically. Everything needed to build a working Dailymotion → 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 Dailymotion 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 Dailymotion 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 Dailymotion 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.

---

Dailymotion API at a glance

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

---

How do I authenticate with the Dailymotion API?

The Dailymotion API uses OAuth 2.0. Protected resources require an 'Authorization' header with a Bearer token: 'Authorization: Bearer <ACCESS_TOKEN>'.

1. Get your credentials

To obtain Dailymotion API credentials, log in to your Dailymotion Studio account (requires Owner or Admin privileges). Navigate to the Organization menu, select API keys, and click Create API key. Choose the appropriate key type (Public or Private), provide the required metadata (title, description, and callback URL if applicable), and click Create. For Private keys, be sure to copy and store the API secret immediately, as it is only displayed once.

2. Add them to .dlt/secrets.toml

Copy
[sources.dailymotion_source]
client_id = "your_api_key_from_dashboard"
client_secret = "your_api_secret_if_applicable"
redirect_uri = "your_registered_callback_url"

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

These are the Dailymotion endpoints dlt can load into DuckDB:

---

How do I load only new Dailymotion records?

Dailymotion exposes page on v2/videos, 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": "videos", "endpoint": {
    "path": "v2/videos",
    "data_selector": "list",
    "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 Dailymotion pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /v2/me and /v2/videos from the Dailymotion API into DuckDB:

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

@dlt.source
def dailymotion_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.dailymotion.com/v2",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "videos", "endpoint": {"path": "v2/videos", "data_selector": "list"}},
            {"name": "playlists", "endpoint": {"path": "v2/playlists", "data_selector": "list"}}
        ],
    }
    yield from rest_api_resources(config)


def load_dailymotion_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="dailymotion_pipeline",
        destination="duckdb",
        dataset_name="dailymotion_data",
    )
    load_info = pipeline.run(dailymotion_source())
    print(load_info)


if __name__ == "__main__":
    load_dailymotion_to_duckdb()

Run it with python dailymotion_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 Dailymotion 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("dailymotion_pipeline").dataset()
df = data.videos.df()
print(df.head())

SQL:

Copy
SELECT * FROM dailymotion_data.videos LIMIT 10;

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

---

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