Device42 Python API Docs | dltHub

Build a Device42-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

Device42's REST API allows data entry, editing, and retrieval. The main endpoint to add a new device is via POST to https://YOURDEVICE42.com/api/1.0/devices/. Authentication and sample code are available in the API documentation. The REST API base URL is https://d42app.device42.pvt and The Device42 API supports both Basic Authentication and Token Authentication, where a Bearer token is used for subsequent API calls..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Device42 data in under 10 minutes.


What data can I load from Device42?

Here are some of the endpoints you can load from Device42:

ResourceEndpointMethodData selectorDescription
devices/api/1.0/devices/GETGet a list of devices
cables/api/1.0/cables/GETGet a list of cables
buildings/api/1.0/buildings/GETGet a list of buildings
rooms/api/1.0/rooms/GETGet a list of rooms
doql/api/2.0/dbb/GETExecute a D42 Object Query Language (DOQL) query

How do I authenticate with the Device42 API?

To authenticate, send a POST request to the /tauth/1.0/token/ endpoint using Basic authentication with your Client key as the username and Client Secret key as the password. The successful response will contain a token, which should then be used as a Bearer token in the Authorization header for all subsequent API calls.

1. Get your credentials

The documentation refers to 'Client key', 'Client Secret key', 'USER', and 'PASSWORD' as credentials. These are typically obtained from your Device42 appliance or dashboard, but specific step-by-step instructions for their retrieval are not detailed in the provided documentation.

2. Add them to .dlt/secrets.toml

[sources.device42_source] client_key = "your_client_key_here" client_secret = "your_client_secret_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Device42 API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python device42_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline device42_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset device42_data The duckdb destination used duckdb:/device42.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline device42_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads devices and rooms from the Device42 API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

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://d42app.device42.pvt", "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 get_data() -> None: pipeline = dlt.pipeline( pipeline_name="device42_pipeline", destination="duckdb", dataset_name="device42_data", ) load_info = pipeline.run(device42_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("device42_pipeline").dataset() sessions_df = data.devices.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM device42_data.devices LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("device42_pipeline").dataset() data.devices.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Device42 data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for Device42?

Request dlt skills, commands, AGENT.md files, and AI-native context.