Patroni Python API Docs | dltHub
Build a Patroni-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Patroni's REST API is used internally for leader elections and by patronictl for failovers. It provides endpoints for managing PostgreSQL clusters. The latest documentation is available for version 4.1.0. The REST API base URL is http://<host>:<port> and Safe GET endpoints are unauthenticated unless TLS + client certs are enforced; unsafe endpoints (POST/PUT/PATCH/DELETE) can be protected with HTTP Basic auth via restapi.authentication.username/password; mutual TLS optional for full protection..
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 Patroni data in under 10 minutes.
What data can I load from Patroni?
Here are some of the endpoints you can load from Patroni:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| patroni | /patroni | GET | General node status; contains key "replication" (array) for replicas. | |
| cluster | /cluster | GET | members | Cluster topology; response JSON has "members" array. |
| metrics | /metrics | GET | Prometheus metrics endpoint (not JSON). | |
| health | /health | GET | Returns HTTP status code 200 only when PostgreSQL is up and running. | |
| primary | /primary | GET | Returns HTTP status code 200 only when the Patroni node is running as the primary with leader lock. | |
| replica | /replica | GET | Replica health check endpoint; returns HTTP status code 200 only when the Patroni node is in the state running, the role is replica and noloadbalance tag is not set. | |
| read_only | /read-only | GET | Health-check endpoint. | |
| standby_leader | /standby-leader | GET | Returns HTTP status code 200 only when the Patroni node is running as the leader in a standby cluster. |
How do I authenticate with the Patroni API?
Unsafe endpoints (POST/PUT/PATCH/DELETE) can be protected with HTTP Basic authentication by setting restapi.authentication.username and restapi.authentication.password parameters. Safe GET endpoints are unauthenticated by default, but can be protected by enabling TLS and optionally requiring client certificates.
1. Get your credentials
API credentials (username and password for HTTP Basic auth) are configured directly within the Patroni configuration file using the restapi.authentication.username and restapi.authentication.password parameters. There is no separate dashboard for obtaining these credentials.
2. Add them to .dlt/secrets.toml
[sources.patroni_source] username = "your_username_here" password = "your_password_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 Patroni 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 patroni_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline patroni_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset patroni_data The duckdb destination used duckdb:/patroni.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline patroni_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 patroni and cluster from the Patroni 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 patroni_source(username, password=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://<host>:<port>", "auth": { "type": "http_basic", "username, password": username, password, }, }, "resources": [ {"name": "patroni", "endpoint": {"path": "patroni"}}, {"name": "cluster", "endpoint": {"path": "cluster", "data_selector": "members"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="patroni_pipeline", destination="duckdb", dataset_name="patroni_data", ) load_info = pipeline.run(patroni_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("patroni_pipeline").dataset() sessions_df = data.patroni.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM patroni_data.patroni LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("patroni_pipeline").dataset() data.patroni.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 Patroni 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 Patroni?
Request dlt skills, commands, AGENT.md files, and AI-native context.