The Vonage Account API (account-api) lets you manage a Vonage (formerly Nexmo) communications account programmatically. It exposes balance checks, auto-reload top-ups, default SMS and delivery-receipt callback configuration, registered email sender management, and full lifecycle control over the API secrets attached to each Vonage API key. The 8 endpoints cover the operational surface needed to keep a messaging or voice account funded, configured, and credentialed.
8 endpointsThe Vonage Application API V2 (application-api) is the current management surface for Vonage Applications — the container that bundles webhook URLs, signing keys, and capability flags across Voice, Messages, RTC, and Verify. It is backwards compatible with v1 applications. The 5 endpoints provide create, list, retrieve, update, and delete operations against /v2/applications and return the public key plus capability webhooks needed to drive Vonage's product APIs.
5 endpointsThe Vonage Application API V2 (application.v2) is the current management surface for Vonage Applications — the container that bundles webhook URLs, signing keys, and capability flags across Voice, Messages, RTC, and Verify. It is backwards compatible with v1 applications. The 5 endpoints provide create, list, retrieve, update, and delete operations against /v2/applications and return the public key plus capability webhooks needed to drive Vonage's product APIs.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"find live events near a location"
# → Jentic returns the GET /events tool with parameter schema, agent executes.