DialNexa · OAuth Scopes

DialNexa OAuth Scopes

OAuth 2.0 searched

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

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.

Voice AIAI AgentsTelephonyLead QualificationMultilingual
Scopes: 0 Flows: Method: searched

Scopes (0)

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

📄 Provider scope reference: https://dialnexa.com/docs/mcp-tools/overview

Source

OAuth Scopes

Raw ↑ 
generated: '2026-09-03'
method: searched
source: https://api.dialnexa.com/.well-known/oauth-authorization-server + https://dialnexa.com/docs/mcp-tools/overview.md
docs: https://dialnexa.com/docs/mcp-tools/overview
description: >-
  OAuth scopes apply to the MCP surface only. The REST /v1 API uses dashboard-provisioned API keys
  (bearer) and declares no oauth2 securityScheme in its OpenAPI; the dialnexa.com
  oauth-authorization-server metadata says plainly that public OAuth token issuance is not
  available for the REST API. The api.dialnexa.com authorization server (OAuth 2.1,
  authorization-code + PKCE S256, PAR, DPoP) issues tokens for the MCP endpoint
  https://api.dialnexa.com/v1/mcp.
oauth_surface: https://api.dialnexa.com/v1/mcp
authorization_server: https://api.dialnexa.com
scopes:
- name: mcp:read
  description: Read DialNexa workspace data through MCP tools.
- name: mcp:write
  description: Run state-changing MCP tools after any tool-specific confirmation requirements are satisfied.
- name: offline_access
  description: Let a compatible client refresh access without re-authenticating every request.
- name: openid
  description: OpenID Connect scope advertised by the authorization server metadata (id_token issuance).
scope_count: 4
notes:
- OAuth grants are tied to the approving user AND the workspace chosen on the consent screen; tool arguments cannot switch workspaces.
- API-key Bearer auth is the alternative for MCP clients that support custom headers; the key resolves the workspace.

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