LanceDB · OAuth Scopes

LanceDB OAuth Scopes

OAuth 2.0 derived

LanceDB 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 /oauth/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.

Vector DatabaseMultimodalLance FormatLakehouseRAGAgent MemoryOpen SourceEmbeddingsFull-Text SearchHybrid SearchColumnar StorageArrowAI Infrastructure

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
/oauth/token

Flows
clientCredentials

Scopes (0)

LanceDB 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.

LanceDB does not publish OAuth scopes; all requests to LanceDB Cloud/Enterprise APIs authenticate with an x-api-key header and no scope-based permissions are documented (https://docs.lancedb.com/api-reference/rest).

📄 Provider scope reference: https://docs.lancedb.com/api-reference/rest

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/lance-namespace-openapi.yaml
docs: https://docs.lancedb.com/api-reference/rest
note: LanceDB does not publish OAuth scopes; all requests to LanceDB Cloud/Enterprise
  APIs authenticate with an x-api-key header and no scope-based permissions are
  documented (https://docs.lancedb.com/api-reference/rest).
schemes:
- name: OAuth2
  source: openapi/lance-namespace-openapi.yaml
  flows:
  - flow: clientCredentials
    tokenUrl: /oauth/token
scopes: []