Vonage APIs for AI Agents
CommunicationsChat MessagingSms MessagingMixed ProvenanceBearer tokenBasic authAPI keyNo authAgent Ready
For Agents
APIs19 in catalogue
Endpoints104 indexed
AuthBearer token / Basic auth / API key / No auth
ProvenanceMixed provenance
An agent can send SMS, voice, and cross-channel messages, run 2FA verification, provision and configure virtual numbers and applications, and pull activity reports, all against a single Vonage account. It can also enrich phone numbers, check pricing before sending, and run compliance tasks such as audit-event retrieval and record redaction.
Vonage exposes each communications capability as a discrete API rather than one monolith, so an agent binds messaging, voice, verification, and number provisioning to the same Vonage application and account. Messages routes SMS, WhatsApp, Viber, and Messenger through one send endpoint, and Dispatch layers automatic channel failover on top of it.
Use for: Sending SMS, voice, and multi-channel messages, running phone verification, provisioning numbers and applications, and managing Vonage account reporting, auditing, and compliance
Not supported: inbound webhook handling, carrier number porting, audio transcription, email sending, KYC document checks
Credentials: Most Vonage APIs authenticate with a single Vonage account API key and secret, passed as HTTP Basic or as request parameters, while the application-scoped APIs (Voice, Conversation, and the JWT paths of Messages and Dispatch) additionally require a JWT signed with a Vonage application private key.
Across 19 Vonage APIs: 11 third-party, 8 Jentic-generated, all indexed by Jentic and kept validated and agent-ready.
Vonage (formerly Nexmo) is a communications platform whose APIs cover SMS, voice, multi-channel messaging, phone verification, number provisioning, and the account, application, reporting, and compliance surfaces that support them. This directory groups 19 Vonage APIs under the nexmo.com domain, spanning outbound SMS and MMS, voice calling with in-call TTS and DTMF control, WhatsApp, Viber, and Facebook Messenger sending, 2FA verification, number search and purchase, phone-number enrichment, activity reporting, audit trails, and GDPR redaction. Together they let a team send and orchestrate messages across channels, run verification flows, manage numbers and applications, and keep an account funded, audited, and compliant.
Vonage API Catalog
19 APIs across 7 product groups.
Communications12
Vonage Conversation APIBuild multi-party chat, voice, SMS, and WebRTC conversations with shared persisted history across 23 endpoints.~23 endpointsNexmo External Accounts APIManage Facebook Messenger, Viber Service Message, and WhatsApp sender accounts and link them to Nexmo applications.~9 endpointsSubaccounts APICreate child subaccounts under a primary Vonage account, list and update their settings, and move balance, credit, or virtual numbers between accounts.~9 endpointsVoice APIPlace outbound voice calls, control in-progress calls with TTS, audio streaming, and DTMF, and retrieve historical call records by UUID.~9 endpointsNumbers APISearch Vonage's virtual number inventory, buy and cancel numbers, and configure their inbound SMS and voice webhooks programmatically.~5 endpointsVonage Application API V1Manage legacy Vonage V1 applications - list, create, update, and delete the application objects that route voice calls and webhook events.~5 endpointsVonage Application API V2Provision and manage Vonage v2 applications - the multi-capability container that binds voice, messages, and verify webhooks to a Vonage account.~5 endpointsPricing APIRetrieve outbound SMS and voice pricing per country or per dialing prefix so an agent can estimate spend before sending traffic.~3 endpointsNexmo Conversion APIReport SMS and voice 2FA conversion outcomes back to Nexmo so the platform can tune routing and reliability for future verification traffic.~2 endpointsNexmo Dispatch APISend a message that automatically retries on the next channel (WhatsApp, SMS, Viber, Messenger) when the previous attempt fails or is not read in time.~1 endpointNexmo Messages APISend a message over SMS, MMS, WhatsApp, Viber Service Message, or Facebook Messenger from a single POST endpoint that picks the channel via the request body.~1 endpointSMS APISend transactional and notification SMS messages from a Vonage virtual number or alphanumeric sender to E.164 phone numbers worldwide, with optional Unicode, binary, and delivery-receipt support.~1 endpoint
Security2
Vonage Audit APIRetrieve and filter Vonage account audit events for compliance, SIEM forwarding, and security investigation.~2 endpointsRedact APIRedact the personally identifiable content of a specific Vonage transactional record (SMS, voice call, verification, message) from Vonage's logs.~1 endpoint
Which Vonage API should I use?
| I want to... | Use |
|---|---|
| Send a single message on one channel | Nexmo Messages API |
| Send plain SMS with the simplest parameters | SMS API |
| Reach a recipient with automatic channel failover | Nexmo Dispatch API |
| Run a full 2FA flow with managed PIN and retries | Verify API |
| Send your own OTP code over SMS | SMS API |
| Manage a Vonage application and its capability webhooks | Vonage Application API V2 |
Install Jentic One Beta
Connect the Vonage APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Vonage APIs, 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" | sh2
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" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
Once connected, ask your agent something like: “send a message and verify a phone number with vonage”.
What AI Agents Can Do with Vonage
Each workflow spans multiple Vonage APIs. Jentic routes each operation to the right API automatically.
Provision a number and send from it
Search Vonage inventory for an SMS-capable virtual number, buy it, then send a transactional message from that number. Numbers provisions the sender and SMS delivers the traffic, so an agent can stand up a new sending identity end to end.
Example prompt:
Call numbers-api GET /number/search for an SMS-capable number, POST /number/buy to purchase it, then call sms-api POST /{format} with that number in the from field.
APIs used
Numbers API + SMS API
Validate a number before verifying it
Check that a phone number is valid, mobile, and reachable before starting a 2FA flow, so verification spend is not wasted on malformed or fixed-line numbers. Number Insight validates and Verify runs the PIN challenge.
Example prompt:
Call number-insight-api GET /standard/{format} to confirm the number is a reachable mobile, then call verify-api POST /{format} to send the PIN and POST /check/{format} to validate the code.
APIs used
Number Insight API + Verify API
Estimate spend, fund the account, then report on it
Look up outbound pricing for a destination, confirm the account has enough credit, send traffic, then export an activity report for reconciliation. Pricing and Account gate the send while Reports closes the loop.
Example prompt:
Call pricing-api GET /get-pricing/outbound/sms for the destination, account-api GET /account/get-balance to confirm funds, then after sending call reports POST /v2/reports to export the activity CSV.
APIs used
Pricing API + Vonage Account API + Reports API
Verify a phone number, then report and redact on request
Run a verification, report its conversion outcome so Vonage can tune routing, and later redact the verification record when a data-subject erasure request is approved. Verify runs the flow, Conversion feeds the signal back, and Redact scrubs the record.
Example prompt:
Call verify-api POST /{format} and POST /check/{format}, post the outcome via nexmo-conversion-api POST /sms, then on an erasure request call redact-api POST /transaction with the verify transaction id.
APIs used
Verify API + Nexmo Conversion API + Redact API
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Install Jentic One once, then have your agent find and add any Vonage API from the Jentic directory into your workspace. Instead of wiring HTTP Basic, application JWTs, and several host paths per API by hand, you store your Vonage credentials once in your own instance and the agent calls whichever Vonage API it needs.
Permission scoping
Your own rules in your Jentic One instance decide which Vonage operations an agent may call. You can allow read-only surfaces such as pricing, account balance, or audit events while withholding state-changing ones such as buying numbers, transferring balance, redacting records, or deleting applications until you add them.
Credential isolation
Your Vonage account key and secret and any application private key are stored encrypted by your own Jentic One instance, which assembles the Basic header or mints the per-call JWT at execution time. The raw credentials never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search the Jentic directory by intent, such as send an SMS message, place an outbound voice call, or verify a phone number, and Jentic returns the matching Vonage operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
FAQs
Specific to using Vonage APIs through Jentic.
What can I build across the Vonage APIs?
You can send SMS, voice, and cross-channel messages, run 2FA verification, provision and configure virtual numbers and applications, enrich phone numbers, check pricing, and manage account balance, activity reporting, audit trails, and record redaction. The APIs share a single Vonage account, so messaging, voice, and verification traffic all bill and report against the same balance.
Do all Vonage APIs use the same credentials?
Most use one Vonage account API key and secret, sent as HTTP Basic or as request parameters. The application-scoped APIs such as Voice and Conversation, plus the JWT paths of Messages and Dispatch, also need a JWT signed with a Vonage application private key. One account can hold multiple applications, each with its own key pair.
Should I use SMS API, Messages API, or Dispatch API?
Use the SMS API for plain SMS-only sending with the simplest parameters. Use the Messages API when one endpoint should send across SMS, MMS, WhatsApp, Viber, or Messenger by channel. Use the Dispatch API when a send should automatically retry on the next channel if the first is not delivered or read in time.
What is a Vonage application and when do I need one?
An application is the container that binds webhook URLs, capability flags, and a signing key pair for Voice, Messages, and Verify. You create it with the Application API V2, then reference its application id to mint JWTs for the Voice and Conversation APIs and the JWT paths of Messages and Dispatch. The V1 Application API remains only for inventorying and migrating older applications.
How do the communications and compliance APIs fit together?
The Audit API gives a read-only trail of account changes for compliance and incident review, and the Redact API scrubs PII from a specific transactional record to support right-to-erasure requests. Both operate on the same account whose SMS, voice, and verification traffic the messaging APIs generate, so a compliance agent can trace a change and then redact the underlying record.
Which APIs help an agent control spend before sending?
The Pricing API returns outbound SMS and voice rates per country or dialing prefix, and the Account API exposes the current balance and auto-reload top-up. Together they let an agent estimate the cost of a campaign and confirm the account has enough credit before any traffic flows.
Are these the official Vonage OpenAPI specs?
Vonage does not publish OpenAPI specifications for several of these services, so Jentic generates and maintains those specs and keeps them validated against the live API. The remaining specs are third-party sourced. Either way each API in this directory carries a provenance label so you can see how its spec was produced.
If you need a different Communications vendor
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.