Rill Data Python API Docs | dltHub
Build a Rill Data-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Rill Data provides a cloud-based platform for building, managing, and embedding real-time data dashboards and custom APIs. The REST API base URL is https://api.rilldata.com and all requests require a Bearer token in the 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 add "dlt[hub]" and start loading Rill Data data in under 10 minutes.
What data can I load from Rill Data?
Here are some of the endpoints you can load from Rill Data:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| organizations | /v1/organizations | GET | Lists all organizations managed by admin | |
| organization_members | /v1/organizations/{org}/members | GET | Lists organization members | |
| organization_invites | /v1/organizations/{org}/invites | GET | Lists organization invites | |
| projects | /v1/organizations/{org}/projects | GET | Lists projects for an organization | |
| project_members | /v1/organizations/{org}/projects/{project}/members | GET | Lists members for a project |
How do I authenticate with the Rill Data API?
All requests to Rill Cloud APIs require an Authorization header containing a Bearer token (e.g., 'Authorization: Bearer '). The token can be a user-issued personal access token (prefixed 'rill_usr_') or a service token (prefixed 'rill_svc_').
1. Get your credentials
To obtain authentication credentials for Rill Data, use the Rill CLI. For local development or personal scripting, generate a User Token (Personal Access Token) using the command rill token issue --display-name "MyTokenName". For production systems and service-to-service communication, create a Service Token using rill service create --project . These tokens are passed as Bearer tokens in the Authorization header.
2. Add them to .dlt/secrets.toml
[sources.rill_data_source] rill_api_token = "rill_usr_..." # For user tokens rill_service_token = "rill_svc_..." # For service tokens
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 Rill Data 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 rill_data_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline rill_data_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset rill_data_data The duckdb destination used duckdb:/rill_data.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 v1/organizations//projects//runtime/api/ and v1/orgs//projects//credentials from the Rill Data 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 rill_data_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.rilldata.com", "auth": {"type": "bearer", "token": api_token}, }, "resources": [ {"name": "custom_api_runtime", "endpoint": {"path": "v1/organizations/{org}/projects/{project}/runtime/api/{api_name}"}}, {"name": "custom_api_local", "endpoint": {"path": "v1/instances/default/api/{api_name}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="rill_data_pipeline", destination="duckdb", dataset_name="rill_data_data", ) load_info = pipeline.run(rill_data_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("rill_data_pipeline").dataset() sessions_df = data.custom_api_runtime.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM rill_data_data.custom_api_runtime LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("rill_data_pipeline").dataset() data.custom_api_runtime.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 Rill Data 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 Rill Data?
Request dlt skills, commands, AGENT.md files, and AI-native context.