DialNexa · Authentication Profile

Dialnexa Authentication

Authentication

DialNexa secures its APIs with http across 2 declared security schemes, as derived from its OpenAPI definitions.

Voice AIAI AgentsTelephonyLead QualificationMultilingual

Methods: http Schemes: 2 OAuth flows: API key in:

Security Schemes

bearer http

scheme: bearer

mcp-oauth oauth2

scheme: oauth2.1 authorization-code + PKCE

Source

Authentication Profile

generated: '2026-09-03'
method: searched
source: https://dialnexa.com/docs/api-reference/authentication.md + OpenAPI securitySchemes (13 refined specs)
summary:
  types:
  - http
  styles:
  - bearer-api-key (REST)
  - oauth2.1 (MCP)
schemes:
- name: bearer
  type: http
  scheme: bearer
  sources:
  - openapi/dialnexa-agents-api-openapi.yml
  - openapi/dialnexa-batch-calls-api-openapi.yml
  - openapi/dialnexa-calls-api-openapi.yml
  - openapi/dialnexa-knowledge-base-api-openapi.yml
  - openapi/dialnexa-languages-api-openapi.yml
  - openapi/dialnexa-llms-api-openapi.yml
  - openapi/dialnexa-organization-folders-api-openapi.yml
  - openapi/dialnexa-phone-numbers-api-openapi.yml
  - openapi/dialnexa-transcribers-api-openapi.yml
  - openapi/dialnexa-voices-api-openapi.yml
  - openapi/dialnexa-webhooks-api-openapi.yml
  - openapi/dialnexa-workflow-leads-api-openapi.yml
  - openapi/dialnexa-workflows-api-openapi.yml
  description: Workspace API key sent as the Bearer token on every request. The key is a key_id:secret pair (two
    segments separated by a colon) created in Dashboard -> Settings -> API Keys and shown once; send the FULL value,
    not just the key id. One key per environment is recommended. 401 {statusCode, message, error} on missing/revoked/malformed
    keys. Do not use x-api-key for v1 endpoints.
- name: mcp-oauth
  type: oauth2
  scheme: oauth2.1 authorization-code + PKCE
  applies_to: https://api.dialnexa.com/v1/mcp (MCP surface only; REST issues no public OAuth tokens)
  authorization_server: https://api.dialnexa.com
  metadata: well-known/dialnexa-api-oauth-authorization-server.json
  scopes:
  - mcp:read
  - mcp:write
  - offline_access
  - openid
  sources:
  - https://dialnexa.com/docs/mcp-tools/overview.md
  - https://api.dialnexa.com/.well-known/oauth-authorization-server
docs: https://dialnexa.com/docs/api-reference/authentication
agent_provisioning:
  note: 'DialNexa publishes machine-readable key-provisioning guidance for AI agents: an auth.md addressed to agents
    (authentication/dialnexa-auth.md, from https://dialnexa.com/auth.md) and an agent_auth block in https://dialnexa.com/.well-known/oauth-authorization-server
    naming identity type account_api_key, credential type api_key_bearer, and step-by-step registration instructions.'
webhook_signing:
  header: x-dialnexa-signature
  algorithm: HMAC-SHA256 hex over raw body
  detail: asyncapi/dialnexa-webhooks.yml

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

curl "https://apis.io/api/v1/security/dialnexa-authentication"

All security posture

curl "https://apis.io/api/v1/security?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.