Vonage APIs for AI Agents
CommunicationsChat MessagingSms MessagingMixed ProvenanceBearer tokenbasic, bearerBasic authAPI keyNo authAgent Ready
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
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.
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?
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.
