Five integration paths
Session files (slides, handouts, PDFs) support a one-call multipart upload (
POST .../files/upload, max 50 MB) or direct-to-storage for larger files (up to 500 MB). Scopes: read:sessions / write:sessions. See Uploading session files and the Session Files API overview.Resource model
Transcription data uses four types, all tied to a session:
Responses use the standard envelope:
pagination with current_page, page_size, total_pages, and total_results.
Session & event content
Ready-to-render packs for partners and mobile apps. Not the same as session composition (abstract/parent linking).Get session content
GET /v1/event//sessions//content
List event content
GET /v1/event//content
Event-level artifacts
GET /v1/event//content/event
Get content item
GET /v1/event//content/items/
Transcriptions
List event transcriptions
GET /v1/event//transcriptions
List session transcriptions
GET /v1/event//sessions//transcriptions
Get session transcription
GET /v1/event//sessions//transcriptions/
Create transcription
POST /v1/event//sessions//transcriptions
Session recordings
List session recordings
GET /v1/event//sessions//recordings
Start recording upload
POST /v1/event//sessions//recordings
Get session recording
GET /v1/event//sessions//recordings/
Complete recording upload
POST …/recordings//complete
Session files
Document attachments (PDF, PowerPoint, Word, images). Full playbook: Uploading session files. API overview: Session Files.List session files
GET /v1/event//sessions//files
Simple file upload
POST /v1/event//sessions//files/upload
Direct-to-storage create
POST /v1/event//sessions//files
Complete file upload
POST …/files//complete
Session files guide
Replace, update metadata, delete
Media upload
Start media upload
POST …/media/upload/initiate
Get media item status
GET /v1/event//sessions//media/
Related reference
- Media & Transcriptions guide — step-by-step playbooks
- Uploading session files — PDF and document attachments
- Session Files API overview
- Authentication & scopes

