Application API

Name: Application API API
Brand: Vonage Application API V2
Availability: InStock

★ Only Publicly Available SpecCommunicationsVoice Telephonybasic5 EndpointsREST

For Agents

Provision and manage Vonage v2 applications — the multi-capability container that binds voice, messages, and verify webhooks to a Vonage account.

Quickstart

Get started with 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:
"create a vonage application"

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

Capabilities

What an agent can do with Application API API.

Create a Vonage v2 application bundling voice, messages, RTC, and verify capability webhooks in one call

List paginated v2 applications scoped to the authenticated Vonage account

Update an application's per-capability webhooks and signed webhook secret without rotating its keys

Retrieve an application's public key and capability set before binding a virtual number

GET STARTED

Start building with Application API API

Explore with Jentic

View OpenAPI Spec

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

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

Use Cases

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

★ Provision a multi-channel application

Building a customer service experience that combines voice IVR and WhatsApp messaging requires a single Vonage v2 application with both voice and messages capabilities configured. POST / accepts a capabilities object that declares answer_url, event_url, inbound_url, and status_url per channel. Once created, the same application_id is used to mint JWTs for both the Voice API and the Messages API.

POST / with name 'support-bot', voice capability webhooks, and messages capability webhooks for the support tenant.

Rotate webhook URLs after backend migration

When a backend handler is moved to a new domain, every Vonage v2 application needs its webhook URLs updated. PUT /{id} replaces the capabilities block, preserving the application's signing key and number bindings. A migration script can iterate via GET / and PUT each application in sequence, finishing in minutes.

For each application_id from GET /, PUT /{id} with capabilities.voice.webhooks.answer_url set to the new domain.

Audit application inventory across an account

Compliance reviews require a periodic export of every active application, its enabled capabilities, and its webhook URLs. GET / paginates through the full list. A weekly cron can write the inventory to long-term storage for review against the deployment registry. Roughly half a day of work.

Iterate GET / with page and page_size until exhausted and write each id, name, and capability set to an inventory file.

Agent-driven tenant onboarding

An onboarding agent provisioning a new tenant searches Jentic for 'create a vonage application', loads the POST / schema, and executes with the tenant's webhook URLs and a generated key pair. Jentic's vault holds the API key and secret; the agent never handles the credentials directly.

Search Jentic for 'create a vonage application', load the schema, and POST / with the new tenant's name and capability webhooks.

Key Endpoints

5 endpoints — the 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.

METHOD

PATH

DESCRIPTION

GET

List available applications

POST

Create an application

GET

/{id}

Get an application

PUT

/{id}

Update an application

DELETE

/{id}

Delete an application

GET

List available applications

POST

Create an application

GET

/{id}

Get an application

PUT

/{id}

Update an application

DELETE

/{id}

Delete an application

Why though Jentic?

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

Credential isolation

Vonage uses HTTP Basic auth with API key and API secret. Jentic stores both in the encrypted MAXsystem vault and injects them per call. The agent never sees the raw secret and credentials are scoped per workflow.

Intent-based discovery

Agents search by intent (e.g. 'check my Vonage account balance') and Jentic returns the matching Vonage operation with its input schema, so the agent calls the right endpoint without browsing developer.vonage.com.

Time to first call

Direct integration: 1-2 days for Basic auth, error handling, and balance checks. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Vonage Voice API

Vonage's voice calling API tied to Vonage applications.

Use alongside Application API to register the application that will place or receive calls.

Complementary

Vonage Messages API

Vonage's omnichannel messaging API for SMS, MMS, WhatsApp, Viber, and Facebook Messenger.

Use after creating an Application to send messages bound to that application's credentials.

Complementary

Vonage Numbers API

Vonage's virtual phone number provisioning API.

Use after creating an Application to assign and link Vonage virtual numbers to it.

Alternative

Twilio Accounts API

Twilio's account and subaccount management API.

Choose Twilio Accounts when the agent's primary stack is already Twilio for SMS, voice, or messaging.

Alternative

Plivo API

Plivo's SMS, voice, and account management platform.

Choose Plivo when an agent is already using Plivo for telephony or wants a Vonage alternative.

FAQs

Specific to using Application API API through Jentic.

What authentication does the Vonage Application API V2 use?

It uses HTTP Basic authentication with the Vonage API key and API secret. Jentic stores both in the encrypted MAXsystem vault and injects them per call so the agent never holds the raw secret.

Is the Vonage Application API V2 backwards compatible with v1?

Yes. Vonage states that applications created with v1 can also be managed via v2. The base path is /v2/applications and all v1 application_ids continue to resolve under v2 endpoints.

What are the rate limits for the Vonage Application API V2?

Application management is a control-plane API. Vonage does not publish a hard per-second cap in the spec; treat GET / pagination as eventually consistent and avoid hammering the endpoint in tight loops.

How do I create a v2 application through Jentic with the Vonage Application API V2?

Run pip install jentic, search Jentic for 'create a vonage application', load the POST / schema, and execute with the capabilities object. Credentials are pulled from the vault at call time.

Can I configure messages and voice capabilities on the same application with the Vonage Application API V2?

Yes. POST / and PUT /{id} accept a capabilities object with separate sub-objects for voice, messages, rtc, and verify, each with its own webhook URLs. A single application_id can carry several capabilities at once.

Does the Vonage Application API V2 return a private key on application creation?

Yes. POST / returns a keys.private_key in the response body that you must store immediately — Vonage does not retain it. The matching public_key is queryable via GET /{id} for verification.