Zuplo Python API Docs | dltHub
Build a Zuplo-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Zuplo is a platform that provides an API gateway and developer APIs for managing accounts, environments, and hosting an AI Gateway that exposes an OpenAI‑compatible universal API. The REST API base URL is https://dev.zuplo.com/v1 and All requests require a Bearer API key for authentication..
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 Zuplo data in under 10 minutes.
What data can I load from Zuplo?
Here are some of the endpoints you can load from Zuplo:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| who_am_i | v1/who-am-i | GET | Returns information about the authenticated caller (top‑level JSON object) | |
| models | v1/models | GET | data | OpenAI‑compatible AI Gateway: lists available models (response follows OpenAI spec; models in data array) |
| chat_completions | v1/chat/completions | POST | choices | OpenAI‑compatible chat completions endpoint (AI Gateway) |
| list_environments | v1/environments | GET | (Developer API) list environment objects | |
| list_api_keys | v1/api-keys | GET | (Developer API) list API keys for the account |
How do I authenticate with the Zuplo API?
The Developer API uses API Keys presented as a Bearer token in the Authorization header. AI Gateway requests use the Zuplo environment API key (example: set Authorization: Bearer YOUR_KEY_HERE).
1. Get your credentials
- Sign in to the Zuplo Portal at https://portal.zuplo.com/ 2) From the main account page click the gear (settings) icon 3) Navigate to "API Keys" 4) Create or copy an API Key for use with the Developer API or an environment.
2. Add them to .dlt/secrets.toml
[sources.zuplo_xai_api_source] api_key = "your_zuplo_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 Zuplo 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 zuplo_xai_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline zuplo_xai_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset zuplo_xai_api_data The duckdb destination used duckdb:/zuplo_xai_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline zuplo_xai_api_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 who_am_i and models from the Zuplo 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 zuplo_xai_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://dev.zuplo.com/v1", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "who_am_i", "endpoint": {"path": "v1/who-am-i"}}, {"name": "models", "endpoint": {"path": "v1/models", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="zuplo_xai_api_pipeline", destination="duckdb", dataset_name="zuplo_xai_api_data", ) load_info = pipeline.run(zuplo_xai_api_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("zuplo_xai_api_pipeline").dataset() sessions_df = data.who_am_i.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM zuplo_xai_api_data.who_am_i LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("zuplo_xai_api_pipeline").dataset() data.who_am_i.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 Zuplo 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.
Troubleshooting
Authentication failures
Ensure the Authorization header is present and uses the Bearer scheme: Authorization: Bearer YOUR_KEY_HERE. Developer API keys are managed in the Portal under API Keys.
Rate limits and quotas
Zuplo‑managed proxies and gateways may enforce provider or environment rate limits. When proxied to upstream AI providers, also consider their rate limits.
Pagination
OpenAI‑compatible AI Gateway endpoints follow OpenAI response shapes (models list under the data key). For paginated endpoints use the provider‑specific pagination parameters if present.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
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 Zuplo?
Request dlt skills, commands, AGENT.md files, and AI-native context.