Crescendo · Authentication Profile

Crescendo Authentication

Authentication

Crescendo secures its APIs with apiKey and http across 2 declared security schemes, as derived from its OpenAPI definitions.

CompanyCustomer ExperienceCustomer SupportArtificial IntelligenceAI AgentsContact CenterConversational AIVoice of CustomerMCP
Methods: apiKey, http Schemes: 2 OAuth flows: API key in: query

Security Schemes

bearerAuth http
scheme: bearer
bearerTokenQuery apiKey
· in: query (bearer_token)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-18'
method: searched
source: openapi/crescendo-platform-openapi-original.json
docs: https://docs.crescendo.ai/api-reference/introduction
notes: >
  Bearer API key. Send `Authorization: Bearer $CRESCENDO_API_KEY` (preferred) or
  `?bearer_token=$CRESCENDO_API_KEY`. API keys are tenant-scoped and carry
  prefix:resource.action scopes (e.g. provisioning:users.read, mcp:bots.*).
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - query
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  bearerFormat: API Key
  sources:
  - openapi/crescendo-platform-openapi-original.json
- name: bearerTokenQuery
  type: apiKey
  in: query
  parameter: bearer_token
  description: Alternative to the Authorization header. Prefer the Authorization header whenever
    possible.
  sources:
  - openapi/crescendo-platform-openapi-original.json