> ## 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. # List participant roles > The event's participant roles — the three standard roles (Speaker, Chairperson, Moderator) and every custom role configured for the event — with the ids to use in the `roleIds` filter of `POST /v1/event/{eventId}/participants`. Ordered as the Sessions settings page shows them. Deleted roles are not returned. `is_custom` is `true` for roles the organizer added. `core_role` is the standard category a custom role maps to (`speaker`, `chairperson` or `moderator`); it decides which legacy array the role's participants appear in on `POST /v1/event/{eventId}/sessions`, and is not a display label — use `name`. An event that has never been opened in the Sessions editor may have no roles yet and answers with an empty `results` array. Its participants are still returned by `POST .../participants`, with `roleId: null` on their standard roles until the roles are created. ## OpenAPI ````yaml /api-reference/openapi.yaml get /v1/event/{eventId}/participant-roles 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: Participants description: | Search and retrieve every contact holding a session role on an event — speakers, chairpersons, moderators and custom roles — with the roles each one holds, and list the event's participant roles. - 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}/participant-roles: get: tags: - Participants summary: List participant roles description: | The event's participant roles — the three standard roles (Speaker, Chairperson, Moderator) and every custom role configured for the event — with the ids to use in the `roleIds` filter of `POST /v1/event/{eventId}/participants`. Ordered as the Sessions settings page shows them. Deleted roles are not returned. `is_custom` is `true` for roles the organizer added. `core_role` is the standard category a custom role maps to (`speaker`, `chairperson` or `moderator`); it decides which legacy array the role's participants appear in on `POST /v1/event/{eventId}/sessions`, and is not a display label — use `name`. An event that has never been opened in the Sessions editor may have no roles yet and answers with an empty `results` array. Its participants are still returned by `POST .../participants`, with `roleId: null` on their standard roles until the roles are created. operationId: list-participant-roles parameters: - name: eventId in: path required: true schema: type: integer description: The event ID. responses: '200': description: OK content: application/json: schema: type: object properties: results: type: array items: $ref: '#/components/schemas/EventParticipantRole' examples: withCustomRoles: value: results: - id: 84bd12e5-d5ec-4c64-a604-4051e06c8dc2 name: Speaker name_plural: Speakers slug: speaker core_role: speaker is_custom: false sort_order: 0 created_at: '2026-02-03T18:04:11.120Z' updated_at: '2026-02-03T18:04:11.120Z' - id: 4efeb845-050f-4002-9496-cb586cdf10f2 name: Moderator name_plural: Moderators slug: moderator core_role: moderator is_custom: false sort_order: 2 created_at: '2026-02-03T18:04:11.120Z' updated_at: '2026-02-03T18:04:11.120Z' - id: 52d60237-19db-4bda-a116-8b9fcb6750e9 name: Panelist name_plural: Panelists slug: panelist core_role: speaker is_custom: true sort_order: 3 created_at: '2026-02-10T09:41:52.004Z' updated_at: '2026-02-10T09:41:52.004Z' '401': description: Unauthorized '404': description: Event not found components: schemas: EventParticipantRole: type: object description: | A participant role configured on an event, as returned by `GET /v1/event/{eventId}/participant-roles`. properties: id: type: string format: uuid description: >- Use as a `roleIds` filter value on `POST /v1/event/{eventId}/participants`. name: type: string description: Display name (singular). name_plural: type: string description: Display name (plural). slug: type: string description: Stable programmatic identifier within the event. core_role: type: string enum: - speaker - chairperson - moderator description: The standard category the role maps to. Not a display label. is_custom: type: boolean description: >- `true` for a role the organizer added; `false` for the three standard roles. sort_order: type: integer description: >- Position in the Sessions settings page; results are returned in this order. created_at: type: string format: date-time updated_at: type: string format: date-time 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`. ````