Vectara · OAuth Scopes

Vectara OAuth Scopes

OAuth 2.0 derived

Vectara uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

Tokens are issued from https://auth.vectara.io/oauth2/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

AIAgentsCorporaEmbeddingsEnterprise SearchGenerative AIGrounded GenerationHallucination DetectionLLMMCPRAGRetrievalSearchSemantic SearchVector Search

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://auth.vectara.io/oauth2/token

Flows
clientCredentials

Scopes (0)

Vectara implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Vectara's OAuth 2.0 supports only the client credentials grant and does not use or document OAuth scopes; permissions are governed by role-based access assigned to app clients at creation (https://docs.vectara.com/docs/security/authentication/oauth-2).

📄 Provider scope reference: https://docs.vectara.com/docs/security/authentication/oauth-2

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/vectara-openapi.yml
docs: https://docs.vectara.com/docs/security/authentication/oauth-2
note: >-
  Vectara's OAuth 2.0 supports only the client credentials grant and does not
  use or document OAuth scopes; permissions are governed by role-based access
  assigned to app clients at creation
  (https://docs.vectara.com/docs/security/authentication/oauth-2).
schemes:
- name: OAuth2
  source: openapi/vectara-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.vectara.io/oauth2/token
  description: OAuth 2.0 client credentials flow.
scopes: []