Nasuni · OAuth Scopes

Nasuni OAuth Scopes

OAuth 2.0 derived

Nasuni 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 /auth/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.

CompanyFile StorageHybrid CloudObject StorageEnterprise StorageData ManagementBackup and RecoveryRansomware ProtectionInfrastructureObservabilityMCPagent-native

Scopes: 0 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
/auth/token

Flows
clientCredentials

Scopes (0)

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

The Portal API declares an OAuth 2.0 clientCredentials flow but publishes an EMPTY scopes map, and no operation carries a scope requirement. Authorization is not scope-based: it is role-based and resolved server-side from the caller's Portal IAM role. The permission vocabulary is retrievable at runtime — GET /iam/permissions lists every permission in the system, GET /iam/roles/{role_id}/permissions the set attached to a role, and GET /iam/me the caller's own — but Nasuni publishes no static scope or permission reference page, so there is nothing to search for and enrich. scope_count is a real zero, not a gap in this harvest.

📄 Provider scope reference: https://docs.api.nasuni.com/api/portal/v0/introduction/

Source

OAuth Scopes

generated: '2026-08-26'
method: derived
source: openapi/nasuni-portal-v0-openapi.yml
schemes:
- name: OAuth2ClientCredentials
  source: openapi/nasuni-portal-v0-openapi.yml
  flows:
  - flow: clientCredentials
    tokenUrl: /auth/token
  description: Standard OAuth2 Client Credentials flow (RFC 6749 §4.4). Send `client_id` (service key) and `client_secret`
    (service secret) as form-encoded body parameters to the token endpoint.
scopes: []
name: Nasuni Portal API OAuth scopes
docs: https://docs.api.nasuni.com/api/portal/v0/introduction/
note: 'The Portal API declares an OAuth 2.0 clientCredentials flow but publishes an EMPTY scopes map, and no operation
  carries a scope requirement. Authorization is not scope-based: it is role-based and resolved server-side from
  the caller''s Portal IAM role. The permission vocabulary is retrievable at runtime — GET /iam/permissions lists
  every permission in the system, GET /iam/roles/{role_id}/permissions the set attached to a role, and GET /iam/me
  the caller''s own — but Nasuni publishes no static scope or permission reference page, so there is nothing to
  search for and enrich. scope_count is a real zero, not a gap in this harvest.'
authorization_model: role-based (Portal IAM), not scope-based
runtime_permission_endpoints:
- GET /iam/permissions
- GET /iam/roles
- GET /iam/roles/{role_id}/permissions
- GET /iam/me
scope_count: 0

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