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 ManagementWorkflowsWebhooksREST

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://{tenant}.benchling.com/api/v2/token

Flows
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).

📄 Provider scope reference: https://docs.benchling.com/docs/authentication

Source

OAuth Scopes

generated: '2026-07-11'
method: derived
source: openapi/benchling-lims-openapi.yml
docs: https://docs.benchling.com/docs/authentication
note: 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).
schemes:
- name: appBearerAuth
  source: openapi/benchling-lims-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: https://{tenant}.benchling.com/api/v2/token
  description: Benchling Apps authenticate with OAuth2 client credentials. Exchange client_id/client_secret
    at POST /api/v2/token for a Bearer access_token.
scopes: []