Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Communications / Nexmo / Nexmo Application API
Nexmo Application API logo

Nexmo Application API

Browse all Nexmo APIs
79
AI ReadinessAI-Ready (A-)79/100
See full scorecard
Community OpenAPI document · agent-readyCommunicationsVoice TelephonyapiKey5 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Manage legacy Vonage V1 applications - list, create, update, and delete the application objects that route voice calls and webhook events.

Use for: List my Vonage applications, Create a new Vonage application for voice, Get the webhook configuration for application id abc, Update the answer_url on a Vonage application

Not supported: Does not place calls, send SMS, provision numbers, or generate JWTs - use for Vonage V1 application object lifecycle only.

The Vonage Application API V1 (application) provides CRUD operations for Vonage Applications, the container resource that binds voice answer URLs, event callback URLs, and assigned virtual numbers. This V1 surface is deprecated by Vonage in favour of v2 at /v2/applications, but remains useful for inventory and migration. The 5 endpoints cover list, create, retrieve, update, and delete on the application resource.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Nexmo Application API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Nexmo Application API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnexmo.com%2Fvonage-application" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnexmo.com%2Fvonage-application" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Nexmo Application API.

List all Vonage applications registered against an account for inventory and audit

Create a new Vonage application that bundles voice answer and event webhook URLs

Retrieve a single application's webhook configuration before routing inbound calls

Update an existing application's voice or event callback URLs without recreating it

Delete a deprecated application once its virtual numbers have been migrated off

Use Cases

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

★ Inventory existing applications before v2 migration

Vonage Applications V1 is deprecated and v2 is the supported version. Before migrating, an operator needs a full list of v1 applications and their webhook URLs to plan recreation in v2. GET / returns paginated applications with answer_url, event_url, and assigned numbers, allowing a migration script to replay them against the v2 endpoint. Effort is roughly half a day including webhook validation.

Call GET / to enumerate all v1 applications and write each one's name, answer_url, and event_url to a migration manifest.

Update webhook URL after a backend redeploy

When the answer or event handler is redeployed at a new URL, every affected Vonage application needs its callback URLs updated. PUT /{app_id} accepts new answer_url and event_url values without disturbing the application's private key or assigned numbers. A small script can sweep all affected app_ids in minutes.

PUT /{app_id} for each impacted application_id, replacing answer_url with https://api.example.com/voice/answer.

Decommission deprecated v1 application

Once a v1 application has been replaced by a v2 equivalent and no numbers remain assigned, it should be deleted to keep the inventory clean. DELETE /{app_id} removes the application; numbers must be unassigned first via the Numbers API. A few minutes per application.

DELETE /{app_id} on the legacy v1 application after confirming no numbers are still bound.

Agent-driven application provisioning

An AI agent provisioning a new tenant needs to create a Vonage application with the correct webhook URLs. Through Jentic, the agent searches for 'create a vonage application', loads the POST / schema, and executes with the tenant-specific URLs. Credentials stay in your Jentic One instance.

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

Key Endpoints

5 endpoints — the vonage application api v1 (application) provides crud operations for vonage applications, the container resource that binds voice answer urls, event callback urls, and assigned virtual numbers.

METHOD

PATH

DESCRIPTION

GET

/

List all applications

POST

/

Create an application

GET

/{app_id}

Retrieve an application

PUT

/{app_id}

Update an application

DELETE

/{app_id}

Delete an application

GET

/

List all applications

POST

/

Create an application

GET

/{app_id}

Retrieve an application

PUT

/{app_id}

Update an application

DELETE

/{app_id}

Delete an application

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

N

Nexmo Application API

- AI-Ready (A-)
79/100
100
Foundational Compliance
68
Developer Experience & Jentic Compatibility
59
AI-Readiness & Agent Experience
94
Agent Usability
100
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

68

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
51%

Example Density

How richly the API is illustrated with examples.

97%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

59

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C+Signals: 4
65%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

71%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1
100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Nexmo Application API by hand means supplying your Vonage key and secret on each call, pointing at the v1/applications host, and managing the application object lifecycle yourself. Through Jentic you install once, import the Nexmo Application API from the API Directory, store the key and secret once, and your agent calls it.

Permission scoping

This API puts the application id in the URL path (/{app_id}), so a rule can pin your agent to one application: it can read and update that application and nothing else. You choose the operations it may call, so application creation and deletion are not included unless you add them.

Credential isolation

Your Vonage API key and secret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list Vonage applications' or 'update an application', and Jentic returns the matching Nexmo Application API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

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 Numbers API

→

Vonage's virtual phone number provisioning API.

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

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.

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 Nexmo Application API through Jentic.

What authentication does the Vonage Application API V1 use?

The OpenAPI spec for Applications V1 does not declare an auth scheme, but in production Vonage requires the API key and secret as query parameters. Jentic stores both in the encrypted Jentic One instance and appends them at call time.

Should I use the Vonage Application API V1 or the v2 Application API?

Vonage marks Applications V1 as deprecated and recommends the v2 Application API at /v2/applications. Use v1 only to inventory or decommission existing applications; create new applications on v2.

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

Application management is a low-frequency control-plane operation. Vonage does not publish a documented per-second cap for these endpoints in the spec; treat list operations as eventually consistent and avoid tight polling loops.

How do I list applications through Jentic with the Vonage Application API V1?

Install the SDK with pip install jentic, search Jentic for 'list vonage applications', load the GET / schema, and execute. Jentic injects the API key and secret from the vault at call time.

Can I update an application's answer_url with the Vonage Application API V1?

Yes. PUT /{app_id} accepts new answer_url and event_url values; the application's private key and number assignments are preserved. Run it through Jentic One, the self-hosted execution layer, to manage Vonage Applications.

Can I limit what my agent is allowed to do with the Vonage Application API?

Yes. Jentic One is self-hosted, so your own rules decide which of the five operations your agent may call and which credentials it may use. Because the application id sits in the URL path, you can pin the agent to a single application so it only reads (GET /{app_id}) and updates (PUT /{app_id}) that one, and you leave listing (GET /), creation (POST /), and deletion (DELETE /{app_id}) out of scope unless you explicitly add them. Your Vonage API key and secret stay in your own instance and are injected only for the operations you permit.

GET STARTED

Start building with Nexmo Application API

Explore with Jentic One
View OpenAPI Document