nexmo.com
Nexmo (now Vonage) exposes multiple HTTP APIs for account, applications, voice, messages, SMS, verify, reports, and conversation, authenticated with either your account API key/secret (as Basic auth or API params, depending on API) or an application-signed JWT for newer APIs like Voice, Messages, and Conversation.
- Nexmo/Vonage Account APIdiscovered
- Nexmo/Vonage Application API v2discovered
- Nexmo/Vonage Voice APIdiscovered
- Nexmo/Vonage Messages APIdiscovered
- Nexmo/Vonage SMS APIdiscovered
- Nexmo/Vonage Verify APIdiscovered
- Nexmo/Vonage Reports APIdiscovered
- Nexmo/Vonage Conversation APIdiscovered
Sign in to the Vonage/Nexmo dashboard account settings. Your account is created with an API key and API secret; many APIs use them either as HTTP Basic credentials (Authorization: Basic base64(API_KEY:API_SECRET)) or as api_key/api_secret request parameters. The CLI can also store them for you with nexmo setup <api_key> <api_secret> as documented in the Nexmo CLI README.
Create a Vonage application in the Applications area of the dashboard and generate/download its private key. Use the application ID plus that private key to mint a JWT for API calls. Vonage's auth docs note that most newer APIs use JWTs and that you can generate them with the CLI; see Authentication.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing