AccuKnox · OAuth Scopes

AccuKnox OAuth Scopes

OAuth 2.0 searched

AccuKnox 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://cspm..accuknox.com/api/v1/o/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.

CompanySecurityCloud SecurityCloud Native Application Protection PlatformKubernetes SecurityRuntime SecurityZero TrustDevSecOpsComplianceAI SecurityVulnerability ManagementContainer Security

Scopes: 0 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://cspm..accuknox.com/api/v1/o/authorize/

Token URL
https://cspm..accuknox.com/api/v1/o/token/

Flows
authorizationCode

Scopes (0)

AccuKnox 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.

AccuKnox documents a real OAuth 2.0 authorization-code surface but publishes NO scope vocabulary. Its OAuth page states that access is governed by role-based authentication on the AccuKnox user profile, not by scopes on the token, and no scopes appear in any authorization request example. scope_count is therefore an honest zero, and NO `OAuthScopes` pointer is wired into apis.yml — a pointer of that name against a document containing no scopes would assert a surface AccuKnox does not publish.

📄 Provider scope reference: https://help.accuknox.com/integrations/oauth/

Source

OAuth Scopes

generated: '2026-09-06'
method: searched
source: https://help.accuknox.com/integrations/oauth/
docs: https://help.accuknox.com/integrations/oauth/
note: >-
  AccuKnox documents a real OAuth 2.0 authorization-code surface but publishes NO scope
  vocabulary. Its OAuth page states that access is governed by role-based authentication on
  the AccuKnox user profile, not by scopes on the token, and no scopes appear in any
  authorization request example. scope_count is therefore an honest zero, and NO
  `OAuthScopes` pointer is wired into apis.yml — a pointer of that name against a document
  containing no scopes would assert a surface AccuKnox does not publish.
scope_count: 0
schemes:
- name: oauth2
  source: https://help.accuknox.com/integrations/oauth/
  flows:
  - flow: authorizationCode
    authorizationUrl: https://cspm.<tenant>.accuknox.com/api/v1/o/authorize/
    tokenUrl: https://cspm.<tenant>.accuknox.com/api/v1/o/token/
scopes: []
authorization_model:
  style: role-based
  evidence: >-
    "role based authentication" on the AccuKnox user profile, per
    https://help.accuknox.com/integrations/oauth/

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/accuknox-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 email required.

GitHub Google LinkedIn

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