VEX V5 Python API Docs | dltHub
Build a VEX V5-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The VEX V5 API is an API reference for VEXcode V5 language bindings (Blocks, Python, C++) that documents in-device/SDK methods for robot programming. The REST API base URL is No REST API base URL found as the documentation describes an SDK, not a web REST API. and No authentication summary found as the documentation describes an SDK, not a web REST API..
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 VEX V5 data in under 10 minutes.
What data can I load from VEX V5?
Here are some of the endpoints you can load from VEX V5:
| No REST API endpoints found in the provided documentation. The VEX V5 API documentation describes an SDK for robot programming, not a web REST API with HTTP GET endpoints returning JSON record lists. |
|---|
How do I authenticate with the VEX V5 API?
No authentication information found as the documentation describes an SDK, not a web REST API.
1. Get your credentials
No instructions for obtaining API credentials found as the documentation describes an SDK, not a web REST API.
2. Add them to .dlt/secrets.toml
[sources.vex_v5_source] No `secrets.toml` example can be provided as no REST API authentication details were found.
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 VEX V5 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 vex_v5_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline vex_v5_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset vex_v5_data The duckdb destination used duckdb:/vex_v5.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline vex_v5_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 No two most commonly used endpoints found as the documentation describes an SDK, not a web REST API. from the VEX V5 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 vex_v5_source(No authentication parameter name found as no REST API authentication details were provided.=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "No REST API base URL found as the documentation describes an SDK, not a web REST API.", "auth": { "type": "No dlt auth type string found as no REST API authentication details were provided.", "No authentication token key found as no REST API authentication details were provided.": No authentication parameter name found as no REST API authentication details were provided., }, }, "resources": [ ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="vex_v5_pipeline", destination="duckdb", dataset_name="vex_v5_data", ) load_info = pipeline.run(vex_v5_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("vex_v5_pipeline").dataset() sessions_df = data.No single endpoint found as the documentation describes an SDK, not a web REST API..df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM vex_v5_data.No single endpoint found as the documentation describes an SDK, not a web REST API. LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("vex_v5_pipeline").dataset() data.No single endpoint found as the documentation describes an SDK, not a web REST API..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 VEX V5 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
No troubleshooting sections for REST API-specific errors found as the documentation describes an SDK, not a web REST API.
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 VEX V5?
Request dlt skills, commands, AGENT.md files, and AI-native context.