Open WebUI Python API Docs | dltHub
Build a Open WebUI-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Open WebUI API endpoints include chat completions and file management. Key endpoints are POST /api/v1/files/ for file uploads and POST /api/v1/knowledge/{id}/file/add for adding files to knowledge bases. Always wait for file processing before adding to knowledge bases. The REST API base URL is https://your-open-webui-instance and All authenticated endpoints require a Bearer token (API key) or JWT..
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 Open WebUI data in under 10 minutes.
What data can I load from Open WebUI?
Here are some of the endpoints you can load from Open WebUI:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| models | /api/models | GET | data | List available models and metadata |
| chats | /api/chats | GET | List user's chat sessions (array of summary objects) | |
| chat | /api/chats/{chat_id} | GET | Retrieve a chat session with full history | |
| files | /api/v1/files | GET | data | List uploaded files (file metadata) |
| knowledge | /api/v1/knowledge | GET | List knowledge bases/collections | |
| health | /health | GET | Health check (public, no auth) | |
| v1_models | /v1/models | GET | OpenAI‑compatible model list |
How do I authenticate with the Open WebUI API?
Include an Authorization: Bearer <API_KEY> header (or JWT) on requests. Some Anthropic‑compatible endpoints also accept x-api-key: <API_KEY>. For multipart uploads set appropriate Content‑Type headers.
1. Get your credentials
- As admin, enable API Keys: Admin Panel → Settings → General → Enable API Keys.
- Grant the appropriate user/group permission to create API keys.
- As a user, go to Profile (bottom‑left) → Settings → Account → API Keys → Generate New API Key.
- Copy the key immediately (it cannot be viewed again).
- Use the key in the
Authorization: Bearer <API_KEY>header.
2. Add them to .dlt/secrets.toml
[sources.open_webui_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 Open WebUI 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 open_webui_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline open_webui_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset open_webui_data The duckdb destination used duckdb:/open_webui.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline open_webui_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 models and chats from the Open WebUI 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 open_webui_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://your-open-webui-instance", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "models", "endpoint": {"path": "api/models", "data_selector": "data"}}, {"name": "chats", "endpoint": {"path": "api/chats"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="open_webui_pipeline", destination="duckdb", dataset_name="open_webui_data", ) load_info = pipeline.run(open_webui_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("open_webui_pipeline").dataset() sessions_df = data.chats.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM open_webui_data.chats LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("open_webui_pipeline").dataset() data.chats.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 Open WebUI 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 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 Open WebUI?
Request dlt skills, commands, AGENT.md files, and AI-native context.