Coactive AI · Authentication Profile

Coactive Ai Authentication

Authentication

Coactive uses HTTP Bearer access tokens. A short-lived (3600s) access token is obtained from POST /api/v0/login by exchanging either a personal token (grant_type refresh_token, presented as a Bearer) or system credentials (grant_type client_credentials, CLIENT_ID:CLIENT_SECRET via HTTP Basic). The resulting access_token is sent as `Authorization: Bearer ` on every request. Access is governed by RBAC roles; SSO/SAML is available for login.

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

CompanyArtificial IntelligenceMultimodal AIComputer VisionVideo UnderstandingImage SearchContextual AdvertisingMediaContent ModerationMetadata
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

HTTPBearer http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: https://docs.coactive.ai/api-reference/authentication/api-authentication
docs: https://docs.coactive.ai/api-reference/authentication/api-authentication
description: >-
  Coactive uses HTTP Bearer access tokens. A short-lived (3600s) access token is
  obtained from POST /api/v0/login by exchanging either a personal token
  (grant_type refresh_token, presented as a Bearer) or system credentials
  (grant_type client_credentials, CLIENT_ID:CLIENT_SECRET via HTTP Basic).
  The resulting access_token is sent as `Authorization: Bearer <token>` on every
  request. Access is governed by RBAC roles; SSO/SAML is available for login.
summary:
  types:
  - http
  token_endpoint: /api/v0/login
  grant_types:
  - client_credentials
  - refresh_token
  access_token_ttl_seconds: 3600
  credential_types:
  - personal_token
  - system_credentials
schemes:
- name: HTTPBearer
  type: http
  scheme: bearer
  sources:
  - openapi/coactive-ai-openapi-original.json