Theta Lake · Authentication Profile

Theta Lake Authentication

Authentication

Theta Lake secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

Communications GovernanceComplianceArchivingSecuritySupervisioneDiscoveryLegal HoldRecords ManagementUnified CommunicationsAI GovernanceRegulatory Compliance
Methods: http, oauth2 Schemes: 2 OAuth flows: clientCredentials API key in:

Security Schemes

BearerAuth http
scheme: bearer
ClientCredentials oauth2
· flows: clientCredentials

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/theta-lake-openapi-original.yml
docs: https://developer.thetalake.ai/
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - clientCredentials
  model: >-
    Create an API key (client_id + client_secret) in the Theta Lake developer portal, exchange it
    at POST /token via the OAuth2 client-credentials grant (RFC 6749) for a short-lived JWT bearer
    access token (expires_in 3600s), then send it as `Authorization: Bearer <jwt>` on every call.
    Tokens are scoped to a workspace and a data center and carry a permissions[] set enforced
    per-operation (see scopes/theta-lake-scopes.yml). GET /token/context returns a token's
    workspace, data_center, type (jwt|oauth|third_party), and granted permissions.
schemes:
- name: BearerAuth
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: JWT bearer API token obtained from the /token endpoint
  sources:
  - openapi/theta-lake-openapi-original.yml
- name: ClientCredentials
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://developer.thetalake.ai/api/v1/token
    token_delivery: request-body (x-www-form-urlencoded; x-receive-token-in request-body)
    grant_type: client_credentials
    scopes: 70
  description: OAuth2.0 client-credentials flow (client_id + client_secret -> JWT)
  sources:
  - openapi/theta-lake-openapi-original.yml