Trino Python API Docs | dltHub
Build a Trino-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The Trino REST API allows clients to submit SQL queries and receive results via HTTP-based protocol calls. The main documentation is found at https://trino.io/docs/current/develop/client-protocol.html. This API is used by CLI, JDBC driver, and other clients. The REST API base URL is http://<trino-coordinator-host>:8080 and Requests require client identity headers; common deployments use HTTP Basic auth or header‑based identity (X‑Trino‑User)..
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 Trino data in under 10 minutes.
What data can I load from Trino?
Here are some of the endpoints you can load from Trino:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| query_results | v1/statement | POST (initial), GET via returned nextUri | data | Submit SQL (POST to /v1/statement). Initial response is QueryResults JSON; if present, 'data' holds rows and 'nextUri' is followed with GET requests. |
| info | v1/info | GET | Coordinator info and version metadata. | |
| node | v1/node | GET | Coordinator node metadata (node id, etc.). | |
| cluster | v1/cluster | GET | Cluster coordinator/worker status (where configured). | |
| query | v1/query/{queryId} | GET | Query status/results overview for a given query id (diagnostic/stats). | |
| status | v1/status | GET | Coordinator status endpoint (if deployed by distribution). |
How do I authenticate with the Trino API?
The Trino client protocol expects client identity in HTTP headers (most importantly X‑Trino‑User). Many Trino deployments are fronted by authenticators (Password, Basic, Kerberos, Certificate, Header) so credentials are provided either as HTTP Basic (Authorization: Basic ...) or via header‑based authenticators (X‑Trino‑User and related headers). Subsequent requests should echo response‑managed headers returned by the coordinator.
1. Get your credentials
- Ask your Trino administrator for a user account or service account.
- If your Trino cluster uses Basic/Password auth, the admin will provide username and password.
- If the cluster uses header authenticator, request a service identity (value for X-Trino-User) and any extra credential name/value the administrator requires.
- If Kerberos or client certificate auth is used, request the Kerberos principal/keytab or TLS client certificate and follow cluster-specific setup steps.
2. Add them to .dlt/secrets.toml
[sources.trino_source] username = "trino_user" password = "trino_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 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 Trino 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 trino_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline trino_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset trino_data The duckdb destination used duckdb:/trino.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline trino_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 query_results and info from the Trino 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 trino_source(username, password=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://<trino-coordinator-host>:8080", "auth": { "type": "http_basic", "password": username, password, }, }, "resources": [ {"name": "query_results", "endpoint": {"path": "v1/statement (initial POST; follow nextUri for GETs)", "data_selector": "data"}}, {"name": "info", "endpoint": {"path": "v1/info"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="trino_pipeline", destination="duckdb", dataset_name="trino_data", ) load_info = pipeline.run(trino_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("trino_pipeline").dataset() sessions_df = data.query_results.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM trino_data.query_results LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("trino_pipeline").dataset() data.query_results.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 Trino 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 Trino?
Request dlt skills, commands, AGENT.md files, and AI-native context.