Benchling · OAuth Scopes
Benchling OAuth Scopes
OAuth 2.0
derived
Benchling 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://{tenant}.benchling.com/api/v2/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.
Life SciencesBiotechLIMSElectronic Lab NotebookRegistryMolecular BiologyInventory ManagementAssay ManagementWorkflowsWebhookREST
Scopes: 0
Flows: clientCredentials
Method: derived
OAuth endpoints
Token URL
https://{tenant}.benchling.com/api/v2/token
https://{tenant}.benchling.com/api/v2/token
Flows
clientCredentials
clientCredentials
Scopes (0)
Benchling 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.
Benchling's OAuth2 client-credentials flow does not use scopes - app permissions are granted by adding the app as a collaborator to organizations, teams, and projects, so a Bearer token can do anything the app has been granted in the UI (https://docs.benchling.com/docs/authentication).
Benchling's OAuth2 client-credentials flow does not use scopes - app permissions are granted by adding the app as a collaborator to organizations, teams, and projects, so a Bearer token can do anything the app has been granted in the UI (https://docs.benchling.com/docs/authentication).
📄 Provider scope reference: https://docs.benchling.com/docs/authentication
Source
OAuth Scopes
Work with this as data
Every scope set here is available over the APIs.io API and to AI agents over MCP.