Druva · OAuth Scopes

Druva OAuth Scopes

OAuth 2.0 searched

Druva publishes 1 OAuth 2.0 scope via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Druva API on a user’s behalf.

Tokens are issued from https://apis.druva.com/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.

BackupCyber ResilienceData ProtectionDisaster RecoverySaaS BackupRansomware RecoveryData GovernanceEnterprise WorkloadsMSPLegal HoldGovCloudMCP

Scopes: 1 Flows: clientCredentials Method: searched

OAuth endpoints

Token URL
https://apis.druva.com/token https://govapis.druva.com/token https://apis.druva.com/msp/auth/v1/token

Flows
clientCredentials

Scopes (1)

Scope	Description	Flows
read	Grants read access. The only scope declared in any Druva specification.

📄 Provider scope reference: https://developer.druva.com/docs/authentication

Source

OAuth Scopes

generated: '2026-09-06'
method: searched
source: openapi/druva-aws-native-openapi.json, openapi/druva-cyber-resilience-govcloud-openapi.json, openapi/druva-cyber-resilience-openapi.json,
  openapi/druva-enterprise-workloads-govcloud-openapi.json, openapi/druva-enterprise-workloads-openapi.json,
  openapi/druva-insync-cloud-openapi.json, openapi/druva-insync-govcloud-openapi.json, openapi/druva-job-management-cloud-openapi.json,
  openapi/druva-job-management-govcloud-openapi.json, openapi/druva-msp-openapi.json, openapi/druva-platform-openapi.json
schemes:
- name: OAuth2
  source: openapi/druva-aws-native-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/token
- name: OAuth2
  source: openapi/druva-cyber-resilience-govcloud-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://govapis.druva.com/token
- name: OAuth2
  source: openapi/druva-cyber-resilience-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/token
- name: OAuth2
  source: openapi/druva-enterprise-workloads-govcloud-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/token
- name: OAuth2
  source: openapi/druva-enterprise-workloads-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/token
- name: OAuth2
  source: openapi/druva-insync-cloud-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/token
- name: OAuth2
  source: openapi/druva-insync-govcloud-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/token
- name: OAuth2
  source: openapi/druva-job-management-cloud-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/token
- name: OAuth2
  source: openapi/druva-job-management-govcloud-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/token
- name: OAuth2
  source: openapi/druva-msp-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/msp/auth/v1/token
- name: BearerAuth
  source: openapi/druva-platform-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://apis.druva.com/token
scopes:
- name: read
  description: Grants read access. The only scope declared in any Druva specification.
  source: securitySchemes.OAuth2.flows.clientCredentials.scopes in 11 of 19 specs
docs: https://developer.druva.com/docs/authentication
note: 'Druva declares exactly ONE OAuth scope across its whole 970-operation estate: ''read'', on the
  client-credentials flow, in 11 of 19 specifications. The documentation is explicit that this is not
  an oversight but the design - ''The Client Credentials have access to all the OAuth Scopes by default''
  - so scope is not the authorization boundary. The real boundary is the Druva console role attached to
  the API credential (Cloud Administrator, or the newer Cloud Admin Read Only role for the inSync Cloud
  and Platform APIs), which is not expressed in any contract. An agent therefore cannot request least
  privilege at the token endpoint; least privilege has to be provisioned by a human when the credential
  is minted. The separate MCP server at mcp.druva.com does scope properly - mcp:tools and mcp:resources
  - and is the only Druva surface where scope carries meaning.'
mcp_scopes:
- name: mcp:tools
  source: https://mcp.druva.com/.well-known/oauth-authorization-server
- name: mcp:resources
  source: https://mcp.druva.com/.well-known/oauth-authorization-server
authorization_model:
  style: role-based, provisioned out of band
  roles:
  - Cloud Administrator
  - Cloud Admin Read Only
  docs: https://help.druva.com/en/articles/8580838-create-and-manage-api-credentials

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/druva-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.