LucidLink · OAuth Scopes

LucidLink OAuth Scopes

OAuth 2.0 searched

LucidLink 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.lucidlink.com/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.

CompanyCloud StorageFile StreamingFile CollaborationMedia and EntertainmentObject StorageDeveloper PlatformMCPAgentic AIZero-Knowledge EncryptionIdentity and Access Management
Scopes: 0 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://auth.lucidlink.com/oauth2/token
Flows
clientCredentials

Scopes (0)

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

📄 Provider scope reference:

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-25'
method: searched
source: >-
  openapi/lucidlink-service-api.json securityDefinitions, plus a documentation search for a
  scopes or permissions reference across support.lucidlink.com and www.lucidlink.com
docs: null
docs_note: >-
  No scopes or permissions reference page exists. LucidLink's Help Center has no article on
  API scopes, and the Service Accounts article states the opposite — that for the initial
  release a service account "inherits the full permissions/scope of a workspace
  administrator, granting access to all available API functionalities".
schemes:
- name: standard
  api: LucidLink Service API v1
  source: openapi/lucidlink-service-api.json
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://auth.lucidlink.com/oauth2/token
scopes: []
scope_count: 0
finding: >-
  LucidLink declares an OAuth2 client-credentials flow with an EMPTY scopes map and applies
  it globally. There is no way for a client to request less than everything: one credential
  reaches domain creation and deletion, filespace creation and deletion, and billing —
  including PATCH /billing/payment, which overwrites the payment instrument on the account.
  For an agent-mediated integration that is the sharpest edge on this API.
partial_mitigation:
  name: Collaborator Service Accounts (beta)
  since: build 3.7.8584 (2026-08-08)
  detail: >-
    Scopes automation to specific folders and filespaces rather than to full admin. It
    applies to the service-account bearer model on the Management API, not to the OAuth2
    credentials on the public Service API, and it is API-only with no UI in beta.
  docs: https://support.lucidlink.com/hc/en-us/articles/48014583746573-Collaborator-Service-Accounts-Beta

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this
  • find_scopesBrowse and filter every scope set in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This scope set 
curl "https://apis.io/api/v1/scopes/lucidlink-scopes"
All oauth scopes 
curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.