video_id per video.
Local file & URL upload examples
Local MCAP Uploads
Upload local.mcap files through the same upload() helper. The initial response
contains an mcap_ingest_id; wait for completion to retrieve the derived videos.
Local MCAP upload
S3 MCAP Cloud Ingest
For large MCAPs already stored in S3, create a role-based S3 Storage Transfer integration, then pass thes3://...mcap URI to upload(). This avoids routing
the source MCAP through your local machine or the Nomadic backend before storage
transfer starts.
S3 MCAP cloud ingest
Multi-view (local/URL)
Use a dict mapping view names to local files or URLs.front is required in every set.
video_id.
- Metadata sidecars must share the same base filename as the video (e.g.,
launch.mp4+launch.json). See the Metadata Ingestion Spec for the full schema. - Custom names (
nameparam) are supported for single files, URLs, and batch dict syntax — not for cloud imports or multi-view. - Folders are auto-created if they don’t exist. Defaults to personal scope; use
scope="org"for shared org folders.
Optional Parameters:
Returns: Dict (single) or List[Dict] (multiple) with
{"video_id": "...", "status": "processing" | "uploaded" | ...}