Clumio · Authentication Profile

Clumio Authentication

Authentication

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

CompanyDataBackupData ProtectionDisaster RecoveryCloudStorageSecurityCompliance
Methods: http Schemes: 1 OAuth flows: API key in: header

Security Schemes

bearerAuth http
scheme: bearer · in: header ()

Source

Authentication Profile

clumio-authentication.yml Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://help.clumio.com/docs/api-tokens
docs: https://help.clumio.com/docs/api-tokens
summary:
  types: [http]
  http_scheme: bearer
  bearer_format: JWT
  api_key_in: [header]
  oauth2_flows: []
  note: >-
    Clumio authenticates every REST API request with a long-lived, signed JSON Web Token (JWT)
    passed as a bearer token in the Authorization header. There is no OAuth2 authorization-server
    flow; tokens are minted from the Clumio UI (Account Settings > API Tokens) and remain valid
    until manually refreshed or deleted. Clumio recommends refreshing tokens every three months.
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearer_format: JWT
  in: header
  header: Authorization
  value_format: 'Bearer <token>'
  sources: [https://help.clumio.com/docs/api-tokens]
token_types:
- name: Personal Token
  purpose: Development and testing. Inherits the same permissions and access as the associated user.
- name: Service Token
  purpose: Production automation and third-party integrations. Not tied to an interactive user.
example: |
  curl -X GET https://us-west-2.api.clumio.com/users \
    -H 'Authorization: Bearer ${BEARER_TOKEN}'