Mender Python API Docs | dltHub
Build a Mender-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Mender provides a REST API for interacting with the Mender server, enabling device management, deployments, and configuration via microservices. The REST API base URL is https://hosted.mender.io/api and all authenticated requests require a Bearer token in the Authorization header.
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 add "dlt[hub]" and start loading Mender data in under 10 minutes.
What data can I load from Mender?
Here are some of the endpoints you can load from Mender:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| devices | /api/management/v2/devauth/devices | GET | Returns a list of devices. | |
| inventory_devices | /api/management/v2/inventory/devices | GET | Returns a paged collection of device inventory data. | |
| search_devices | /api/management/v2/inventory/filters/search | POST | Searches devices based on inventory attributes. | |
| device_details | /api/management/v2/devauth/devices/{id} | GET | Returns details for a specific device. | |
| device_count | /api/management/v2/devauth/devices/count | GET | Returns the total count of devices. |
How do I authenticate with the Mender API?
Requests requiring authentication must include an 'Authorization' header containing a JSON Web Token (JWT) in the format 'Bearer {access-token}'. For management APIs, the token is obtained via the login endpoint; for device APIs, via the authenticate device endpoint.
1. Get your credentials
To obtain credentials for the Mender REST API, you can either log in using your username and password or generate a Personal Access Token (PAT). To log in, make a POST request to /api/management/v1/useradm/auth/login using Basic Authentication (username and password). For long-lived programmatic access, generate a Personal Access Token via the Mender web UI in the 'My profile' section, or by sending a POST request to /api/management/v1/useradm/settings/tokens while authenticated with a valid JWT token. Once obtained, include the token in your API calls using the 'Authorization: Bearer {access-token}' header.
2. Add them to .dlt/secrets.toml
[sources.mender_source] mender_api_token = "your_personal_access_token_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 init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub 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:
uv run dlthub ai toolkit install rest-api-pipeline
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 Mender 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:
uv run python mender_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline mender_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset mender_data The duckdb destination used duckdb:/mender.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub 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 /api/management/v1/useradm/auth/login and /api/management/v1/useradm/settings/tokens from the Mender 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 mender_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://hosted.mender.io/api", "auth": {"type": "bearer", "token": api_token}, }, "resources": [ {"name": "devices", "endpoint": {"path": "api/management/v2/devauth/devices"}}, {"name": "search_devices", "endpoint": {"path": "api/management/v2/inventory/filters/search"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="mender_pipeline", destination="duckdb", dataset_name="mender_data", ) load_info = pipeline.run(mender_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("mender_pipeline").dataset() sessions_df = data.devices.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM mender_data.devices LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("mender_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 Mender data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Mender?
Request dlt skills, commands, AGENT.md files, and AI-native context.