Load Ovh data to DuckDB

OVHcloud API is a RESTful web service that allows customers to manage and configure OVHcloud products programmatically. Everything needed to build a working Ovh → 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 Ovh 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 Ovh 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 Ovh 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.

---

Ovh API at a glance

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

---

How do I authenticate with the Ovh API?

Authentication is performed by passing an OAuth2 or Personal Access Token in the Authorization header as a Bearer token (e.g., 'Authorization: Bearer ').

1. Get your credentials

1. Navigate to the OVHcloud token creation page (e.g., https://api.ovh.com/createToken/ or the US equivalent https://api.us.ovhcloud.com/createToken/).\n2. Log in with your OVHcloud account ID (or sub-user account ID) and password.\n3. Enter an application name and description.\n4. Define the access rules (Rights) by selecting the HTTP methods and paths. Use an asterisk (*) for the path to allow full access to a chosen method.\n5. Click Create keys. The dashboard will generate and display three mandatory tokens: Application Key (AK), Application Secret (AS), and Consumer Key (CK). Store these securely.

2. Add them to .dlt/secrets.toml

Copy
[sources.ovh_source]
access_token = "REPLACE_ME"

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

These are the Ovh endpoints dlt can load into DuckDB:

---

How do I load only new Ovh records?

Ovh exposes X-Pagination-Cursor-Next on v2/iam/policy, 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": "iam_policy", "endpoint": {
    "path": "v2/iam/policy",
    "incremental": {"cursor_path": "X-Pagination-Cursor-Next", "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 Ovh pipeline look like?

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

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

@dlt.source
def ovh_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://eu.api.ovh.com/1.0/",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "iam_policy", "endpoint": {"path": "v2/iam/policy"}},
            {"name": "cloud_ssh_keys", "endpoint": {"path": "v2/cloud/project/{serviceName}/sshkey"}}
        ],
    }
    yield from rest_api_resources(config)


def load_ovh_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="ovh_pipeline",
        destination="duckdb",
        dataset_name="ovh_data",
    )
    load_info = pipeline.run(ovh_source())
    print(load_info)


if __name__ == "__main__":
    load_ovh_to_duckdb()

Run it with python ovh_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 Ovh 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("ovh_pipeline").dataset()
df = data.iam_policy.df()
print(df.head())

SQL:

Copy
SELECT * FROM ovh_data.iam_policy LIMIT 10;

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

---

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