Load CLO 3D data to DuckDB

CLO 3D provides a REST API to facilitate interactions with its headless environment, enabling tasks such as file exports and data retrieval through HTTP methods like GET, POST, and PUT. Everything needed to build a working CLO 3D → 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 CLO 3D 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 CLO 3D 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 CLO 3D 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.

---

CLO 3D API at a glance

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

---

How do I authenticate with the CLO 3D API?

Authentication is typically handled using a Bearer token passed in the request headers. The credential is provided via a configuration secret.

1. Get your credentials

To obtain API credentials for the CLO-SET platform (which serves as the backend for data access via REST API), perform the following steps: 1. Sign in to your CLO-SET account at https://www.clo-set.com/. 2. Navigate to your account settings or the developer portal within the dashboard to generate an API access token. 3. Use this token as a Bearer Token in your request headers for authentication. If you do not have an account, you must first register at the platform to access the API.

2. Add them to .dlt/secrets.toml

Copy
[sources.clo_3d_source]
access_token = "your_bearer_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 CLO 3D data can I load into DuckDB?

These are the CLO 3D endpoints dlt can load into DuckDB:

---

How do I load only new CLO 3D records?

CLO 3D exposes updated_at on v2/styles, 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": "styles", "endpoint": {
    "path": "v2/styles",
    "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 CLO 3D pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading customers and files from the CLO 3D API into DuckDB:

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

@dlt.source
def clo_3d_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.clo3d.com/",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "styles", "endpoint": {"path": "v2/styles", "data_selector": "results"}},
            {"name": "workrooms", "endpoint": {"path": "v2/workrooms", "data_selector": "results"}}
        ],
    }
    yield from rest_api_resources(config)


def load_clo_3d_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="clo_3d_pipeline",
        destination="duckdb",
        dataset_name="clo_3d_data",
    )
    load_info = pipeline.run(clo_3d_source())
    print(load_info)


if __name__ == "__main__":
    load_clo_3d_to_duckdb()

Run it with python clo_3d_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 CLO 3D 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("clo_3d_pipeline").dataset()
df = data.styles.df()
print(df.head())

SQL:

Copy
SELECT * FROM clo_3d_data.styles LIMIT 10;

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

---

How do I deploy the CLO 3D 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 CLO 3D 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 CLO 3D 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