Skip to main content
The Sessionboard Public API supports two authentication methods:
  1. API Tokens — Long-lived tokens for server-to-server integrations and scripts
  2. OAuth 2.1 — For AI assistants (Claude, ChatGPT) and user-authorized connections
API tokens are scoped to your organization and can be generated from the Sessionboard admin dashboard.

Generate a Token

1

Open Organization Settings

Log in to the Sessionboard admin dashboard and navigate to Organization Settings from the sidebar.
2

Navigate to API Tokens

Select the API Tokens section within your organization settings.
3

Generate a New Token

Click Generate Token. Give the token a descriptive name and select the appropriate scopes for your use case.
4

Copy the Token

Copy the generated token immediately. For security reasons, the full token value is only displayed once. Store it securely in your application’s environment variables or secrets manager.

Using the Token

Include the token in the x-access-token header on every API request.
Keep your API tokens secure. Never commit tokens to source control, embed them in client-side code, or share them in public channels. If a token is compromised, revoke it immediately from the API Tokens settings page and generate a new one.

Token Scopes

API tokens can be granted specific scopes to control access:Legacy tokens (empty scopes array) get all read scopes implicitly but do not get write access. When generating a token, select only the scopes your integration requires.Scoped read tokens must include the domain-specific read scope for each API area — for example, read:events alone does not grant access to transcription, media, or session file endpoints. Those require read:transcriptions, read:media, or read:sessions respectively.