Confluent Python API Docs | dltHub

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

Last updated:

The Confluent REST APIs allow for managing and interacting with Kafka clusters and stream processing through RESTful endpoints. The Processor API enables custom processor definitions and state store interactions. The Kafka REST APIs facilitate producing and consuming messages to/from Kafka clusters. The REST API base URL is https://<REST-endpoint>/kafka/v3 and All requests require HTTP Basic authentication using a Confluent Cloud API key and secret..

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


What data can I load from Confluent?

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

ResourceEndpointMethodData selectorDescription
clusters/kafka/v3/clustersGETdataList clusters available to this REST endpoint
topics/kafka/v3/clusters/{cluster_id}/topicsGETdataList topics in a cluster
topics_configs/kafka/v3/clusters/{cluster_id}/topics/-/configsGETdataList configuration parameters for all topics
consumer_groups/kafka/v3/clusters/{cluster_id}/consumer-groupsGETdataList consumer groups for a cluster
consumers/kafka/v3/clusters/{cluster_id}/consumer-groups/{consumer_group_id}/consumersGETdataList consumers in a consumer group
consumer_lags/kafka/v3/clusters/{cluster_id}/consumer-groups/{consumer_group_id}/lagsGETdataList consumer lags for a group
restproxy_consumers_subscription/consumers/{group_name}/instances/{instance}/subscriptionGETtopicsReturns { "topics": [ ... ] }
restproxy_consumers_records/consumers/{group_name}/instances/{instance}/recordsGETReturns a top‑level array of record objects

How do I authenticate with the Confluent API?

Create a cluster‑scoped API key and secret in Confluent Cloud, combine them as "key:secret", Base64‑encode the string, and send it in the Authorization header as Basic . The header also requires standard Accept and Content-Type fields.

1. Get your credentials

  1. Open the Confluent Cloud Console and select your cluster.
  2. Navigate to Cluster Settings → API Keys.
  3. Click Create Key to generate a new cluster‑scoped API key and secret.
  4. Record the key and secret; combine them as ":" and Base64‑encode the string.
  5. Use the encoded string in the HTTP Authorization header: Authorization: Basic <encoded>.

2. Add them to .dlt/secrets.toml

[sources.confluent_source] api_key = "your_api_key_here" api_secret = "your_api_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 Confluent 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 confluent_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline confluent_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 topics and clusters from the Confluent 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 confluent_source(api_key, api_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<REST-endpoint>/kafka/v3", "auth": { "type": "http_basic", "username/password": api_key, api_secret, }, }, "resources": [ {"name": "topics", "endpoint": {"path": "kafka/v3/clusters/{cluster_id}/topics", "data_selector": "data"}}, {"name": "clusters", "endpoint": {"path": "kafka/v3/clusters", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="confluent_pipeline", destination="duckdb", dataset_name="confluent_data", ) load_info = pipeline.run(confluent_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("confluent_pipeline").dataset() sessions_df = data.topics.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM confluent_data.topics LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("confluent_pipeline").dataset() data.topics.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 Confluent 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 Confluent?

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