Benchling · OAuth Scopes

Benchling OAuth Scopes

OAuth 2.0 searched

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 WorkflowsRESTWebhook
Scopes: 0 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
/api/v2/token /oauth/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 defines NO OAuth scopes — confirmed twice over. The clientCredentials flow declares an empty `scopes: {}` object in both the v2 and the v3 OpenAPI, and the authentication docs state the model plainly: "anything a user has permission to do through the UI, the user's API Key or OIDC token or application's OAuth Bearer token has permission to do through the API." Authorization is membership-based, not scope-based.

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

Source

OAuth Scopes

Raw ↑ 
generated: '2026-08-15'
method: searched
source: openapi/benchling-v3-openapi.yaml + openapi/*.yml (securitySchemes) and the permissions section
  of https://docs.benchling.com/docs/authentication, read 2026-08-15.
schemes:
- name: oAuth
  source: openapi/benchling-aa-sequences-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-apps-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-assay-results-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-assay-runs-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-audit-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-authentication-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-blobs-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-boxes-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-codon-usage-tables-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-connect-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-containers-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-custom-entities-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-custom-notations-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-data-frames-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-datasets-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-dna-alignments-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-dna-oligos-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-dna-sequences-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-dropdowns-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-entities-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-entries-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-enzymes-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-events-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-exports-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-feature-libraries-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-files-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-folders-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-instrument-queries-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-inventory-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-lab-automation-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-label-templates-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-legacy-requests-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-legacy-workflows-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-legacy-workflows-deprecated-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-locations-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-mixtures-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-molecules-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-monomers-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-nucleotide-alignments-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-oligos-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-organizations-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-plates-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-printers-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-projects-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-registry-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-rna-oligos-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-rna-sequences-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-schemas-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-tasks-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-teams-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-users-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-v3-openapi.yaml
  flows:
  - flow: clientCredentials
    tokenUrl: /oauth/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-warehouse-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-workflow-flowchart-config-versions-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-workflow-flowcharts-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-workflow-outputs-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-workflow-task-groups-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
- name: oAuth
  source: openapi/benchling-workflow-tasks-api-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /api/v2/token
  description: OAuth2 Client Credentials flow intended for service access
scopes: []
docs: https://docs.benchling.com/docs/authentication
scope_count: 0
note: 'Benchling defines NO OAuth scopes — confirmed twice over. The clientCredentials flow declares an
  empty `scopes: {}` object in both the v2 and the v3 OpenAPI, and the authentication docs state the model
  plainly: "anything a user has permission to do through the UI, the user''s API Key or OIDC token or
  application''s OAuth Bearer token has permission to do through the API." Authorization is membership-based,
  not scope-based.'
authorization_model:
  mechanism: organization / team / project membership
  principals:
  - user (API key or OIDC id token)
  - Benchling App (service principal, client credentials)
  default_app_access: A newly created app belongs to no organization, team or project and can access NO
    data until an admin grants it membership.
  revocation:
    suspended_user: Suspending a user in Benchling invalidates their API key. Suspending them only in
      the IdP does NOT.
    archived_app: Archiving an app blocks API access; unarchiving restores it without a new client secret.
    note: If a suspended user held an app's credentials, rotate the app client secret — apps are not tied
      to a user and are not suspended with them.
  docs: https://docs.benchling.com/docs/authentication

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/benchling-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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