Clariva logoClariva/ API
Sign in
DocsAuthentication

Authentication

API Key Authentication

All protected Clariva v1 endpoints use bearer API keys. Keys are tied to an organization and enforced server-side for voice and generation ownership boundaries.

Header format

bashAuthorization2 lines
curl -X GET 'https://app.clariva.ai/api/v1/voices' \
  -H 'Authorization: Bearer cv_live_***********************************'

Key checklist

  • - Key format must match cv_live_<token>.
  • - Send with Authorization: Bearer <API_KEY>.
  • - Each key is organization scoped.
  • - Revoked keys return 403 FORBIDDEN.
  • - Expired keys return 401 UNAUTHORIZED.

Create keys in Dashboard -> Settings -> API Keys. Raw key values are shown once at creation time.

Key handling policy

Store keys in server environment variables and rotate periodically. Treat keys like passwords and never commit them to source control.

Failure mapping

StatusCodeMeaning
401UNAUTHORIZEDMissing header, invalid format, invalid key, or expired key.
403FORBIDDENKey is revoked or blocked from resource scope.

Search documentation

Find pages, endpoints, and sections.