> ## Documentation Index > Fetch the complete documentation index at: https://apidocs.sessionboard.com/llms.txt > Use this file to discover all available pages before exploring further. # Update session file metadata > Updates display title and/or assigned participant. Does not change file bytes — use `replace` for that. Unknown fields are ignored. Requires `write:sessions`. ## OpenAPI ````yaml /api-reference/openapi.yaml put /v1/event/{eventId}/sessions/{sessionId}/files/{fileId} openapi: 3.1.0 info: title: Sessionboard Public API version: '1.0' description: >- REST API for managing sessions, speakers, contacts, sponsors, exhibitors, and event data on the Sessionboard platform. contact: name: Sessionboard Support email: support@sessionboard.com termsOfService: https://www.sessionboard.com/legal/terms-of-service servers: - url: https://public-api.sessionboard.com description: US Region - url: https://public-api-eu.sessionboard.com description: EU Region security: - ApiKey: [] - BearerToken: [] tags: - name: Events description: Manage events on the platform. - name: Sessions description: Search and retrieve sessions within an event. - name: Session Writes description: >- Create, update, delete, and restore sessions. Requires the `write:sessions` scope. - name: Contact Writes description: >- Create, update, delete, and restore contacts. Requires the `write:contacts` scope. - name: Exhibitor Writes description: >- Create, update, delete, and restore exhibitors. Requires the `write:exhibitors` scope. - name: Sponsor Writes description: >- Create, update, delete, and restore sponsors. Requires the `write:sponsors` scope. - name: Field Writes description: >- Create, update, and delete custom fields. Requires the `write:fields` scope. - name: Speakers description: Search and retrieve speakers within an event. - name: Contacts description: Search and retrieve contacts at the organization or event level. - name: Sponsors description: Search and retrieve sponsors within an event. - name: Exhibitors description: Search and retrieve exhibitors within an event. - name: Event Settings description: >- Retrieve event configuration such as fields, tags, tracks, rooms, formats, levels, languages, and session statuses. - name: GDPR description: Manage GDPR data access and erasure requests. - name: Insights description: >- Query event data using SbQL, generate queries with AI, and manage dashboards. - name: Metadata Writes description: >- Create, update, and delete session metadata (rooms, tracks, tags, formats, levels, languages, statuses). Requires the `write:metadata` scope. - name: Agenda Planning description: >- Manage agenda drafts, draft sessions, scheduling rules, and evaluation personas. Requires the `write:events` scope. - name: Dashboards & Widgets description: >- Create, read, update, and delete dashboards and widgets at the event or organization level. Requires `write:events` scope for writes. - name: Reports & Queries description: >- Create, read, update, delete, and run saved SbQL queries/reports at the event or organization level. Requires `write:events` scope for writes. - name: Transcriptions description: >- Transcript text on sessions — fragments, summaries, insights, and translations. Requires `read:transcriptions` / `write:transcriptions` scopes. - name: Session Recordings description: >- Session audio files for recording archives (live capture or imported audio). Requires `read:transcriptions` / `write:transcriptions` scopes. - name: Media description: >- Upload video or audio files for automatic transcription. Requires `read:media` / `write:media` scopes. - name: Session Files description: > Documents attached to sessions (PDFs, PowerPoint, Word, images, and similar). Simple upload: `POST .../files/upload` (multipart, max 50 MB). Direct-to-storage: create → PUT → complete (max 500 MB). Requires `read:sessions` / `write:sessions` scopes. See the [Uploading session files](/guides/uploading-session-files) guide. - name: OAuth description: >- OAuth 2.1 endpoints for AI client authorization (Claude, ChatGPT). Mounted at `/oauth/` (not `/v1/`). paths: /v1/event/{eventId}/sessions/{sessionId}/files/{fileId}: put: tags: - Session Files summary: Update session file metadata description: | Updates display title and/or assigned participant. Does not change file bytes — use `replace` for that. Unknown fields are ignored. Requires `write:sessions`. operationId: update-session-file parameters: - $ref: '#/components/parameters/EventId' - $ref: '#/components/parameters/SessionId' - $ref: '#/components/parameters/FileId' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SessionFileUpdateRequest' responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/SessionFileResponse' '400': description: Validation error '403': description: Missing write:sessions scope '404': description: File not found components: parameters: EventId: name: eventId in: path required: true schema: type: integer description: Event ID SessionId: name: sessionId in: path required: true schema: type: string format: uuid description: Session UUID FileId: name: fileId in: path required: true schema: type: string format: uuid description: Session file (Content) UUID schemas: SessionFileUpdateRequest: type: object properties: title: type: string nullable: true assigned_participant_id: type: string format: uuid nullable: true SessionFileResponse: type: object properties: data: $ref: '#/components/schemas/Content' Content: type: object description: >- A content attachment (file, document, or media) associated with a session. properties: id: type: string format: uuid url: type: string format: uri title: type: string filename: type: string size: type: integer mimetype: type: string created_at: type: string format: date-time updated_at: type: string format: date-time assigned_participant_id: type: string format: uuid nullable: true description: Contact UUID of the session participant this file is assigned to. assigned_participant_email: type: string format: email nullable: true assigned_participant_name: type: string nullable: true securitySchemes: ApiKey: type: apiKey in: header name: x-access-token description: >- Organization API token. Generate from Organization Settings → API Tokens. BearerToken: type: http scheme: bearer description: >- OAuth 2.1 access token. Obtained via the OAuth PKCE flow at `/oauth/token`. ````