Apache Pinot Python API Docs | dltHub

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

Last updated:

Apache Pinot is a distributed OLAP datastore designed to provide low-latency, real-time analytics by ingesting data from streaming and batch sources. The REST API base URL is http://localhost:9000 and requests require an 'Authorization' header with Basic or Bearer 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 add "dlt[hub]" and start loading Apache Pinot data in under 10 minutes.


What data can I load from Apache Pinot?

Here are some of the endpoints you can load from Apache Pinot:

ResourceEndpointMethodData selectorDescription
tables/tablesGETtablesList all tables in the Pinot cluster
table_config/tables/{tableName}GETGet the configuration of a specific table
query_sql/query/sqlPOSTresultTable.rowsSubmit SQL query to the broker
cursor_store/responseStoreGETList active cursor response stores
cursor_results/responseStore/{requestId}/resultsGETrowsFetch additional cursor pages with offset
cursor_metadata/responseStore/{requestId}GETFetch cursor metadata

How do I authenticate with the Apache Pinot API?

Authentication uses HTTP Basic Auth or Bearer tokens provided via the 'Authorization' header. The header format is typically 'Basic <base64_encoded_credentials>' or 'Bearer '

1. Get your credentials

Apache Pinot does not have a native dashboard for generating API keys. By default, Pinot Controller and Broker REST APIs are unauthenticated. To enable security, you must configure Basic Auth on the Pinot cluster or deploy an external reverse proxy (e.g., Nginx) or API gateway (e.g., OAuth proxy) in front of the Pinot services. If Basic Auth is enabled in the cluster, credentials (username and password) are managed via Pinot configuration files. For production environments, consult your infrastructure team to obtain credentials from your specific authentication provider or proxy gateway.

2. Add them to .dlt/secrets.toml

[sources.apache_pinot_source] # No built-in auth exists; provide credentials only if using a reverse proxy # username = "your_username" # password = "your_password"

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 Apache Pinot 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 apache_pinot_pipeline.py

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

Pipeline apache_pinot_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset apache_pinot_data The duckdb destination used duckdb:/apache_pinot.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 query/sql and cluster/configs from the Apache Pinot 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 apache_pinot_source(auth_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:9000", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": auth_token}, }, "resources": [ {"name": "cursor_results", "endpoint": {"path": "responseStore/{requestId}/results", "data_selector": "rows"}}, {"name": "tables", "endpoint": {"path": "tables", "data_selector": "tables"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="apache_pinot_pipeline", destination="duckdb", dataset_name="apache_pinot_data", ) load_info = pipeline.run(apache_pinot_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("apache_pinot_pipeline").dataset() sessions_df = data.query_sql.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM apache_pinot_data.query_sql LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("apache_pinot_pipeline").dataset() data.query_sql.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 Apache Pinot 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 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 Apache Pinot?

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