Quickwit Python API Docs | dltHub
Build a Quickwit-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Quickwit is a high-performance search engine for log management and observability that provides a REST API for indexing, searching, and cluster management. The REST API base URL is http://<quickwit_node_host>:<port>/api/v1 and no native authentication provided by the service; implemented at the infrastructure layer.
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 Quickwit data in under 10 minutes.
What data can I load from Quickwit?
Here are some of the endpoints you can load from Quickwit:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| indexes | /api/v1/indexes | GET | Gets all indexes metadata. | |
| search | /api/v1/{index}/search | GET | hits | Search for documents in an index. |
| node_info | /api/v1/node | GET | Get node configuration and info. | |
| indexing | /api/v1/indexing | GET | Observe indexing pipeline status. | |
| health | /health/readyz | GET | Readiness check. |
How do I authenticate with the Quickwit API?
Quickwit does not provide built-in authentication for its REST API. Users are typically expected to secure access via network/firewall configurations or by placing the service behind a reverse proxy that handles authentication headers.
1. Get your credentials
Quickwit does not natively manage API keys or user credentials at the application level. To secure your Quickwit REST API, you must deploy the Quickwit node behind a reverse proxy (such as Nginx, Traefik, or an AWS Application Load Balancer). Follow these steps: 1. Deploy your Quickwit instance in a private network or behind a reverse proxy. 2. Configure the proxy to enforce authentication (e.g., Basic Authentication, Bearer token, or mTLS). 3. Generate your credentials (username/password or token) within the proxy's configuration management system. 4. Use these proxy-managed credentials when configuring your dlt source to include them in the HTTP headers.
2. Add them to .dlt/secrets.toml
[sources.quickwit_source] api_base = "https://your-proxy-domain.com/api/v1" auth_username = "your_username" auth_password = "your_password" # If using a Bearer token: # auth_token = "Bearer your_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 Quickwit 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 quickwit_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline quickwit_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset quickwit_data The duckdb destination used duckdb:/quickwit.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 /indexes and /{index_id}/search from the Quickwit 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 quickwit_source(api_base=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://<quickwit_node_host>:<port>/api/v1", "auth": {"type": "api_key", "api_key": api_base}, }, "resources": [ {"name": "search", "endpoint": {"path": "api/v1/{index}/search", "data_selector": "hits"}}, {"name": "indexes", "endpoint": {"path": "api/v1/indexes"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="quickwit_pipeline", destination="duckdb", dataset_name="quickwit_data", ) load_info = pipeline.run(quickwit_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("quickwit_pipeline").dataset() sessions_df = data.search.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM quickwit_data.search LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("quickwit_pipeline").dataset() data.search.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 Quickwit 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 Quickwit?
Request dlt skills, commands, AGENT.md files, and AI-native context.