Sendbird · Authentication Profile

Sendbird Authentication

Authentication

Sendbird secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

apiTokenAuth apiKey
· in: header (Api-Token)

Source

Authentication Profile

Raw ↑ 
generated: '2026-06-20'
method: searched
source: openapi/sendbird-platform-openapi.yml
docs: https://sendbird.com/docs/chat/platform-api/v3/prepare-to-use-api
summary:
  types:
  - apiKey
  api_key_in:
  - header
token_model:
  - name: master API token
    description: Auto-generated when an application is created; cannot be revoked or modified. Sent in the Api-Token header.
  - name: secondary API tokens
    description: Generated and managed via the Platform API; revocable. Sent in the Api-Token header.
  - name: session/access tokens
    description: Per-user tokens for client-side authentication (issued via user create / token endpoints).
guidance: >-
  The Platform API is server-side only. Sendbird docs warn: "DON'T send any Chat
  API requests from your client app" — use per-user session tokens on clients.
schemes:
- name: apiTokenAuth
  type: apiKey
  in: header
  parameter: Api-Token
  description: Sendbird master or secondary API token obtained from the Sendbird Dashboard.
  sources:
  - openapi/sendbird-platform-openapi.yml