Session files are not the media or recording upload flow. Use Media & Transcriptions for video/audio that should be transcribed or stored as session recordings.
Upload paths
- Simple (≤ 50 MB)
- Direct to storage (≤ 500 MB)
One multipart call — Sessionboard detects size and MIME type, scans the file, and returns the attached
Content object.POST .../files/uploadwith multipart fieldfile- Optional form fields:
title,assigned_participant_id
Scopes
| Action | Scope |
|---|---|
| List files | read:sessions |
| Upload / create / complete / replace / update / delete | write:sessions |
Endpoints
Simple upload
POST /v1/event//sessions//files/upload
List session files
GET /v1/event//sessions//files
Start direct upload
POST /v1/event//sessions//files
Complete direct upload
POST …/files//complete
Replace file bytes
POST …/files//replace
Update metadata
PUT /v1/event//sessions//files/
Response shape
File objects use theContent schema (id, url, title, filename, size, mimetype, assigned participant fields, timestamps). Direct-to-storage create/replace responses also include an upload object with url, method, and headers for the presigned PUT.
Related reference
- Uploading session files — full playbook
- Transcriptions & Media
- Authentication & scopes