Load Device42 data to DuckDB

Device42 is a comprehensive IT infrastructure management and CMDB platform providing RESTful APIs for data entry, editing, and retrieval. Everything needed to build a working Device42 → 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 Device42 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 Device42 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 Device42 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.

---

Device42 API at a glance

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

---

How do I authenticate with the Device42 API?

The API supports Basic authentication and token-based authentication. For token-based auth, send a POST request to /tauth/1.0/token/ using Basic credentials to retrieve a token, then use it as a Bearer token in the Authorization header.

1. Get your credentials

Device42 supports two primary authentication methods: User Authentication (Basic Auth) and Token Authentication (Bearer token). For production deployments, Token Authentication is recommended. To use this, you must generate a Client Key and Client Secret. Access these by logging into your Device42 appliance dashboard, navigating to the user profile or API management section (as detailed in your specific appliance version documentation at api.device42.com), and requesting/generating API credentials. For simpler or legacy setups, you can also use your Device42 administrator username and password directly via Basic Authentication.

2. Add them to .dlt/secrets.toml

Copy
[sources.device42_source]
base_url = "https://your-device42-appliance-url"
client_key = "your_client_key_here"
client_secret = "your_client_secret_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 Device42 data can I load into DuckDB?

These are the Device42 endpoints dlt can load into DuckDB:

---

How do I load only new Device42 records?

The Device42 API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "devices", "endpoint": {
    "path": "api/1.0/devices/",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "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 Device42 pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /api/1.0/devices/ and /api/1.0/rooms/ from the Device42 API into DuckDB:

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

@dlt.source
def device42_source(client_key_client_secret=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.device42.com/",
            "auth": {"type": "bearer", "token": client_key_client_secret},
        },
        "resources": [
            {"name": "devices", "endpoint": {"path": "api/1.0/devices/"}},
            {"name": "rooms", "endpoint": {"path": "api/1.0/rooms/"}}
        ],
    }
    yield from rest_api_resources(config)


def load_device42_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="device42_pipeline",
        destination="duckdb",
        dataset_name="device42_data",
    )
    load_info = pipeline.run(device42_source())
    print(load_info)


if __name__ == "__main__":
    load_device42_to_duckdb()

Run it with python device42_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 Device42 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("device42_pipeline").dataset()
df = data.devices.df()
print(df.head())

SQL:

Copy
SELECT * FROM device42_data.devices LIMIT 10;

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

---

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