Cybus Connectware Python API Docs | dltHub

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

Last updated:

Cybus Connectware is an industrial IoT platform that provides a REST API for managing services, resources, and system status. The REST API base URL is https://api.cybus.io/v2 and All requests require a Bearer token supplied 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 pip install "dlt[workspace]" and start loading Cybus Connectware data in under 10 minutes.


What data can I load from Cybus Connectware?

Here are some of the endpoints you can load from Cybus Connectware:

ResourceEndpointMethodData selectorDescription
services/api/v2/servicesGETdataRetrieve a list of all services
resources/api/v2/resourcesGETdataRetrieve a list of all resources
service_ids/api/v2/services/idsGETdataRetrieve identifiers of all services
service_detail/api/v2/services/{id}GETdataRetrieve details of a specific service
service_resources/api/v2/services/{serviceId}/resourcesGETdataRetrieve resources belonging to a specific service
resource_detail/api/v2/resources/{resourceId}GETdataRetrieve details of a specific resource

How do I authenticate with the Cybus Connectware API?

The API uses header‑based authentication where the client sends an Authorization: Bearer <api_key> header with each request.

1. Get your credentials

  1. Log in to the Cybus Connectware web portal.
  2. Navigate to SettingsAPI Access.
  3. Click Create New API Key.
  4. Give the key a name, set required scopes, and confirm.
  5. Copy the generated key; it will be shown only once.
  6. Store the key securely and use it as the Bearer token in the Authorization header.

2. Add them to .dlt/secrets.toml

[sources.cybus_connectware_source] api_key = "your_api_key_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 Cybus Connectware 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 cybus_connectware_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline cybus_connectware_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 services and resources from the Cybus Connectware 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 cybus_connectware_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.cybus.io/v2", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "services", "endpoint": {"path": "api/v2/services", "data_selector": "data"}}, {"name": "resources", "endpoint": {"path": "api/v2/resources", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cybus_connectware_pipeline", destination="duckdb", dataset_name="cybus_connectware_data", ) load_info = pipeline.run(cybus_connectware_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("cybus_connectware_pipeline").dataset() sessions_df = data.services.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM cybus_connectware_data.services LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("cybus_connectware_pipeline").dataset() data.services.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 Cybus Connectware 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.


Troubleshooting

Authentication Errors

  • 401 Unauthorized – Returned when the Authorization header is missing or the token is invalid. Verify that the Bearer <api_key> header is correct and not expired.

Rate Limiting

  • 429 Too Many Requests – The API enforces request limits per minute. If received, implement exponential back‑off and respect the Retry-After header.

Pagination Issues

  • Responses include a meta.pagination object. Ensure that your pipeline follows the next link or uses the provided page and size parameters to retrieve all pages. Missing pagination handling can lead to incomplete data extraction.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


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 Cybus Connectware?

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