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 /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 SciencesBiotechR&DMolecular BiologyLaboratory Information ManagementElectronic Lab NotebookAssay ManagementInventory ManagementSequence ManagementExperiment WorkflowsRESTWebhooks

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
/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 OAuth 2.0 client credentials flow does not use scopes; API access is governed by the app's or user's permissions (organization, team, and project membership), per 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-openapi.yaml
docs: https://docs.benchling.com/docs/authentication
note: Benchling's OAuth 2.0 client credentials flow does not use scopes; API access
  is governed by the app's or user's permissions (organization, team, and project
  membership), per https://docs.benchling.com/docs/authentication.
schemes:
- name: oAuth
  source: openapi/benchling-openapi.yaml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
scopes: []