Skip to main content
POST
Upload a session file (simple)

Authorizations

x-access-token
string
header
required

Organization API token. Generate from Organization Settings → API Tokens.

Path Parameters

eventId
integer
required

Event ID

sessionId
string<uuid>
required

Session UUID

Body

multipart/form-data
file
file
required

The file to attach (field name must be file).

title
string

Display title. Defaults to the uploaded filename.

assigned_participant_id
string<uuid>

Contact UUID of a session participant.

content_slot_id
string<uuid>

Optional upload slot this file answers. Same rules as content_slot_id on POST .../files: the slot must be active, apply to the session, accept the file's type and have room; 400 names the slot otherwise. Sets the file's type.

Response

Created — file attached and scanned

data
object

A content attachment (file, document, or media) associated with a session.

Approvals. On events using Approvals (Early Access), a file can be held back until it is approved and its release time has passed. The Session Files endpoints still list a held file, so an integration knows it exists, but return url: null until it is released. Publish only files whose approval_status is approved or not_required. When a file you already published moves to any other status, remove it from your destination.