GreptimeDB Python API Docs | dltHub

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

Last updated:

GreptimeDB's REST API uses http(s)://{{host}}:{{port}}/ as its base URL, supports Basic authentication, and allows SQL queries via http://{{API-host}}/v1/sql. It also supports X-Greptime-Timeout and X-Greptime-Timezone headers. The REST API base URL is http://{{host}}:{{port}}/ and Supports Basic authentication (username:password) via Authorization header..

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


What data can I load from GreptimeDB?

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

ResourceEndpointMethodData selectorDescription
health/healthGETHealth check; returns plain "OK"
status/statusGETServer status information
metrics/metricsGETPrometheus metrics text (plain text)
config/configGETServer configuration (TOML‑like text)
sql/v1/sqlPOST, GEToutput[].records.rowsExecute SQL; JSON responses place rows under output[].records.rows and schema under output[].records.schema.column_schemas
promql/v1/promqlGET, POSToutputPromQL query endpoint returning GreptimeDB JSON‑format frames
prometheus_query/v1/prometheus/api/v1/query_rangeGET, POSTPrometheus‑compat HTTP API endpoints (various paths)
admin_leader/admin/leaderGETReturns leader address as plain text
admin_heartbeat/admin/heartbeatGETtop-level array (example shows nested array: [ [ {..}, {...} ] ])Returns datanode heartbeat records; examples show an array‑of‑arrays with record objects
influxdb_ping/v1/influxdb/pingGETInfluxDB compatibility ping/health

How do I authenticate with the GreptimeDB API?

GreptimeDB HTTP APIs accept Basic auth credentials encoded in Base64. Attach either Authorization: Basic or x-greptime-auth: Basic to requests.

1. Get your credentials

  1. Create or identify a database user and password in GreptimeDB (configured via the server's user provider, e.g. static_user_provider). 2) Combine username and password as "username:password". 3) Base64‑encode that string. 4) Add to requests as header Authorization: Basic or x-greptime-auth: Basic .

2. Add them to .dlt/secrets.toml

[sources.greptime_db_source] 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 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 GreptimeDB 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 greptime_db_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline greptime_db_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 sql and metrics from the GreptimeDB 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 greptime_db_source(auth_basic=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://{{host}}:{{port}}/", "auth": { "type": "http_basic", "password": auth_basic, }, }, "resources": [ {"name": "sql", "endpoint": {"path": "v1/sql", "data_selector": "output[].records.rows"}}, {"name": "metrics", "endpoint": {"path": "metrics"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="greptime_db_pipeline", destination="duckdb", dataset_name="greptime_db_data", ) load_info = pipeline.run(greptime_db_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("greptime_db_pipeline").dataset() sessions_df = data.sql.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM greptime_db_data.sql LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("greptime_db_pipeline").dataset() data.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 GreptimeDB 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 GreptimeDB?

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