Turborepo Python API Docs | dltHub
Build a Turborepo-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Turborepo's API reference covers configuration and caching. The turbo docs command searches Turborepo documentation. The remote cache API documentation is limited. The REST API base URL is https://vercel.com and All requests to the remote cache API require a Bearer token 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 Turborepo data in under 10 minutes.
What data can I load from Turborepo?
Here are some of the endpoints you can load from Turborepo:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| artifacts_status | /v8/artifacts/status | GET | Check remote caching status (server health/version). | |
| artifacts_head | /v8/artifacts/{hash} | HEAD | Check whether an artifact exists (returns 200 if present, 404 if missing). | |
| artifacts_download | /v8/artifacts/{hash} | GET | Download a cache artifact by hash (binary response). | |
| artifacts_upload | /v8/artifacts/{hash} | PUT | Upload a cache artifact (request body is artifact bytes). | |
| artifacts_query | /v8/artifacts | POST | results | Query info about multiple artifacts in one request (response contains 'results' array with per-hash info). |
| analytics | /v8/analytics | GET | (Optional) Analytics endpoints exposed by OpenAPI spec for observability (may require OTEL headers/config). |
How do I authenticate with the Turborepo API?
Turborepo sends/accepts an Authorization: Bearer header (token can be provided via turbo login or the TURBO_TOKEN environment variable). The remote cache may also accept the token provided in server-side configuration; team scoping is passed via teamId or slug query parameters.
1. Get your credentials
- Run
turbo loginto obtain credentials interactively (stores token). 2) Or create/choose a token value for your self-hosted cache and store it in an environment variable named TURBO_TOKEN or in your CI secrets. 3) For Vercel-managed remote cache, use Vercel dashboard / account tokens if applicable.
2. Add them to .dlt/secrets.toml
[sources.turborepo_source] token = "your_bearer_token_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 Turborepo 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 turborepo_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline turborepo_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset turborepo_data The duckdb destination used duckdb:/turborepo.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline turborepo_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 artifacts and artifacts_status from the Turborepo 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 turborepo_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://vercel.com", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "artifacts", "endpoint": {"path": "v8/artifacts/{hash}"}}, {"name": "artifacts_status", "endpoint": {"path": "v8/artifacts/status"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="turborepo_pipeline", destination="duckdb", dataset_name="turborepo_data", ) load_info = pipeline.run(turborepo_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("turborepo_pipeline").dataset() sessions_df = data.artifacts.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM turborepo_data.artifacts LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("turborepo_pipeline").dataset() data.artifacts.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 Turborepo 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 Turborepo?
Request dlt skills, commands, AGENT.md files, and AI-native context.