OptiTrack Python API Docs | dltHub
Build a OptiTrack-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The OptiTrack Motive API allows developers to integrate and use data from OptiTrack's tracking systems. The API includes a quick start guide and function reference for setting up and using the API. Essential steps include configuring settings in Motive and exporting necessary files. The REST API base URL is `` and API access requires a valid Motive license and corresponding hardware/security key; no HTTP authentication is documented..
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 OptiTrack data in under 10 minutes.
What data can I load from OptiTrack?
Here are some of the endpoints you can load from OptiTrack:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| markers | Motive API function: Marker* / Update | native call | Get reconstructed marker (3D) per frame via TT_Update()/MarkerCount/MarkerXYZ functions. | |
| rigid_bodies | Motive API function: RigidBody* | native call | Get rigid body 6DoF pose per frame via RigidBody functions (CreateRigidBody, RigidBodyProperty, etc.). | |
| profile | LoadProfile / SaveRigidBodies | native call | Import/export Motive profile (.motive) and rigid body assets. | |
| natnet_stream | NatNet stream | UDP stream | Live streaming of mocap data over NatNet protocol (binary/structured), not JSON. | |
| vrpn_stream | StreamVRPN | VRPN stream | Streaming via VRPN protocol. | |
| api_results | Motive eResult codes | return value | Function result codes (kApiResult_*) used to detect errors. |
How do I authenticate with the OptiTrack API?
Motive functionality is provided via the native Motive API libraries bundled with the Motive application. Access control is enforced by a Motive license and hardware/security key; there are no documented HTTP headers for REST authentication.
1. Get your credentials
Obtain a Motive license by purchasing Motive from OptiTrack and following their licensing activation process; license activation and hardware/security key provisioning are handled by OptiTrack support and installers. Ensure Motive is installed on a Windows machine and the hardware/security key (dongle) is connected or license activated before using the Motive API.
2. Add them to .dlt/secrets.toml
[sources.optitrack_motive_api_source] license = "YOUR_MOTIVE_LICENSE_OR_KEY_IDENTIFIER"
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 OptiTrack 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 optitrack_motive_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline optitrack_motive_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset optitrack_motive_api_data The duckdb destination used duckdb:/optitrack_motive_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline optitrack_motive_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 markers and rigid_bodies from the OptiTrack 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 optitrack_motive_api_source(license_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "", "auth": { "type": "none_native_sdk", "license": license_key, }, }, "resources": [ {"name": "markers", "endpoint": {"path": "(native) Update / MarkerXYZ / MarkerCount"}}, {"name": "rigid_bodies", "endpoint": {"path": "(native) RigidBody functions (CreateRigidBody / RigidBodyProperty)"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="optitrack_motive_api_pipeline", destination="duckdb", dataset_name="optitrack_motive_api_data", ) load_info = pipeline.run(optitrack_motive_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("optitrack_motive_api_pipeline").dataset() sessions_df = data.markers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM optitrack_motive_api_data.markers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("optitrack_motive_api_pipeline").dataset() data.markers.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 OptiTrack 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 OptiTrack?
Request dlt skills, commands, AGENT.md files, and AI-native context.