Kpow Python API Docs | dltHub

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

Last updated:

Kpow offers a REST API for integrating with Apache Kafka. The API is secure, vendor-agnostic, and supports OpenAPI 3.1. It enables real-time monitoring and management of Kafka resources. The REST API base URL is https://kpow.mycorp.org:3001/kafka/v1 and All requests require an API key for authentication, provided via HTTP Basic authentication..

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 Kpow data in under 10 minutes.


What data can I load from Kpow?

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

ResourceEndpointMethodData selectorDescription
clustersclustersGETclustersGet a list of Kafka clusters
registriesschema-registry/v1/registriesGETregistriesGet a list of schema registries
subjectsschema-registry/v1/registries/{registry_id}/subjectsGETsubjectsGet a list of subjects for a schema registry
versionsschema-registry/v1/registries/{registry_id}/subjects/{subject_name}/versionsGETversionsGet versions of a subject
temporary_policiesadmin/v1/temporary-policiesGETtemporary_policiesGet a list of temporary policies
scheduled_mutationsadmin/v1/scheduled-mutationsGETscheduled_mutationsGet a list of scheduled mutations

How do I authenticate with the Kpow API?

Authentication is performed using HTTP Basic authentication. The API key should be provided as the password, with an empty username, in the Authorization header.

1. Get your credentials

The Kpow documentation states that API keys can be created via JAAS realm.properties or a helper utility. Specific step-by-step instructions for obtaining API credentials from a dashboard are not provided in the available documentation.

2. Add them to .dlt/secrets.toml

[sources.kpow_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 Kpow 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 kpow_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline kpow_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 registries and subjects from the Kpow 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 kpow_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://kpow.mycorp.org:3001/kafka/v1", "auth": { "type": "http_basic", "api_key": api_key, }, }, "resources": [ {"name": "registries", "endpoint": {"path": "schema-registry/v1/registries", "data_selector": "registries"}}, {"name": "subjects", "endpoint": {"path": "schema-registry/v1/registries/{registry_id}/subjects", "data_selector": "subjects"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="kpow_pipeline", destination="duckdb", dataset_name="kpow_data", ) load_info = pipeline.run(kpow_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("kpow_pipeline").dataset() sessions_df = data.clusters.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM kpow_data.clusters LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("kpow_pipeline").dataset() data.clusters.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 Kpow 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 Kpow?

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