Nexmo Application API

Name: Nexmo Application API API
Brand: Nexmo Application API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsProject Managementnone5 EndpointsREST

For Agents

Manage v1 Nexmo applications — the security and configuration container used by Voice and other Nexmo products. Five CRUD endpoints. Marked deprecated; use v2 for new work.

Quickstart

Get started with Nexmo Application API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"list legacy nexmo v1 applications"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Nexmo Application API API.

Create a new Nexmo application via POST / with name, type, answer_url, and event_url

Retrieve all applications belonging to the account via GET /

Retrieve a single application by id via GET /{app_id}

Update an application's URLs or name via PUT /{app_id}

GET STARTED

Start building with Nexmo Application API API

Explore with Jentic

View OpenAPI Document

Use for: Create a new Nexmo application for a Voice integration, List the existing Nexmo applications on this account, Retrieve the configuration for a Nexmo application by id, Update the answer_url on a legacy Nexmo application

Not supported: Does not manage v2 capabilities objects, sign JWTs for application-scoped APIs, or send messages or calls — use only for legacy v1 application CRUD; use Application v2 for new integrations.

Jentic publishes the only available OpenAPI document for Nexmo Application API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Nexmo Application API, keeping it validated and agent-ready. This is version 1 of the Nexmo Application API and is marked deprecated by Vonage in favour of v2; it remains documented here for legacy integrations. A Nexmo application is the security and configuration container that binds together Voice answer URLs, event URLs, public key material, and channel-specific permissions. The five endpoints under /v1/applications cover full CRUD on the application resource: list, create, retrieve, update, and destroy.

Use Cases

Patterns agents use Nexmo Application API API for, with concrete tasks.

★ Auditing legacy v1 applications before migration

Teams preparing to migrate from Application API v1 to v2 first need an inventory of what exists. GET / paginates the legacy applications; GET /{app_id} fetches each one's full configuration including answer_url, event_url, and public_key so the migration script can reconstruct the equivalent v2 capabilities object.

GET / to list applications, then GET /{app_id} for each id to capture answer_url, event_url, and public_key for migration.

Updating answer URLs across legacy applications

When the application's webhook hostname changes, every legacy app's answer_url and event_url need updating. PUT /{app_id} accepts the modified URL fields and returns the updated record. The whole operation is one call per application id obtained from GET /.

GET / to fetch the application list, then PUT /{app_id} for each application with the new answer_url and event_url.

Cleanup of unused legacy applications by an agent

An AI agent tidying up a Nexmo tenant can list v1 applications, identify the ones still pointing at a decommissioned hostname, and DELETE /{app_id} for each. Through Jentic the agent searches once for 'destroy a nexmo application', loads the operation, and executes per id without browsing legacy docs.

Search Jentic for 'destroy a nexmo application v1', load DELETE /{app_id}, iterate the GET / result, and execute DELETE per id.

Key Endpoints

5 endpoints — jentic publishes the only available openapi specification for nexmo application api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

List all applications on the account

POST

Create a new application

GET

/{app_id}

Retrieve a single application by id

PUT

/{app_id}

Update an application's name or URLs

DELETE

/{app_id}

Destroy an application

GET

List all applications on the account

POST

Create a new application

GET

/{app_id}

Retrieve a single application by id

PUT

/{app_id}

Update an application's name or URLs

DELETE

/{app_id}

Destroy an application

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Nexmo basic credentials are stored encrypted in the Jentic vault and are never returned to the agent. Calls to /v1/applications go through scoped execution that adds the auth header server-side.

Intent-based discovery

Agents search by intent (e.g., 'create a nexmo application') and Jentic returns the matching v1 endpoint with its parameters, while clearly indicating v2 is the recommended path for new work.

Time to first call

Direct integration: a few hours for auth and CRUD wrappers. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Nexmo Application API v2

The current, non-deprecated version of the same application management API

Use v2 for any new integration; v1 is only useful for migrating existing legacy applications.

Complementary

Nexmo Messages API

Sends messages bound to the application-scoped JWT this resource configures

Once an application exists, JWTs signed for it are used by Messages to send WhatsApp, Viber, and Messenger traffic.

Alternative

Twilio API

Twilio's Applications resource is the closest equivalent for binding voice and messaging webhooks

Pick Twilio when the underlying voice and messaging traffic already runs through Twilio.

FAQs

Specific to using Nexmo Application API API through Jentic.

Why is there no official OpenAPI spec for Nexmo Application API?

Vonage (formerly Nexmo) does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Nexmo Application API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Nexmo Application API use?

The OpenAPI spec does not declare a securityScheme on the v1 endpoints, but in practice these calls use HTTP basic auth with api_key and api_secret. Through Jentic the credential pair is stored encrypted and injected at execution time.

Should I use this v1 API or v2?

Vonage marks v1 as deprecated and recommends v2 (the application.v2 slug) for new work. v1 remains useful for inventory and migration: GET / lists existing v1 applications and GET /{app_id} fetches their config so migration scripts can rebuild the equivalents in v2.

What are the rate limits for the Nexmo Application API?

The OpenAPI spec does not declare rate limits for /v1/applications. Account-level throttles apply, and application CRUD is typically a low-volume operation relative to message or voice traffic.

How do I update an application's webhook URLs through Jentic?

Search Jentic for 'update a nexmo application', load PUT /{app_id}, and execute with the application id in the path and the new answer_url and event_url in the body.

How do I retrieve the public key associated with an application?

GET /{app_id} returns the application record including the public_key field. Use the same call before destroying the application if the keypair needs to be archived.