Autocloz + Vonage
Vonage (formerly Nexmo) is listed in Autocloz for voice, SMS and WhatsApp. SMS works with the API key and secret on the Settings → Integrations card. Voice and WhatsApp are different: Vonage authenticates those APIs with a JWT signed by your application's private key, and Autocloz does not sign that JWT today. It sends whatever is in the API key field as the bearer token, so a plain API key will be rejected by Vonage. For calls without that caveat use Telnyx.
Status: limited today. Vonage voice and WhatsApp need a pre-signed application JWT in the API key field. The card collects a private key, but Autocloz does not use it to sign one. We have not verified a live Vonage call.
What you can do with Vonage
Vonage plugs into the Call stack — bring your own carrier account, scoped to your workspace.
NCCO call scripts
A call sends an NCCO to Vonage. If you do not supply one, Autocloz sends a single talk action that reads the step text.
SMS with key and secret
Vonage SMS uses the API key and secret directly, which is what the card collects.
Stored per workspace
API key, secret, application ID and private key are encrypted and never shown back in full.
How to connect Vonage
Bring your own carrier account — you keep control of the account, the spend and the data boundary.
- 1
Create a Vonage application
In the Vonage dashboard create an application with Voice (and Messages, for WhatsApp) enabled, and download its private key.
- 2
Fill in the Vonage card
In Settings → Integrations paste the API key, API secret, application ID, private key and from-number.
- 3
Decide how you will authenticate voice
Voice and WhatsApp need a signed JWT in the API key field. A plain API key there will fail with 401 from Vonage.
- 4
Test SMS separately
Send one text from a Vonage SMS sender. That path uses the key and secret and does not need a JWT.
Vonage card fields and their use
API key and API secret feed Vonage SMS. Application ID and private key are the values Vonage uses for Voice and Messages, and they are stored, but the call and WhatsApp adapters authenticate with the API key field alone. From-number is the sender for all three channels. If you only need SMS from Vonage, you can leave the application ID and private key empty.
- Voice: posts an NCCO to Vonage's Voice API with a bearer token.
- SMS: API key and secret, confirmed reaching Vonage on 2026-09-28.
- WhatsApp: Messages API with a bearer token; same JWT caveat as voice.
How the Vonage adapters authenticate
The Vonage Voice API and Messages API (used for WhatsApp) accept a JWT signed with the application's private key. Autocloz's Vonage call and WhatsApp adapters put the stored API key into the Authorization header as a bearer token. They do not mint a JWT from the private key. So those two channels only work if the API key field holds a JWT you signed yourself, and Vonage JWTs expire.
The Vonage SMS adapter is different. It sends the API key and secret as Vonage's SMS API expects, and our 2026-09-28 check confirmed it reaches Vonage with the card's values.
What a Vonage call sounds like
With no custom NCCO the lead hears the step text read aloud by Vonage's text-to-speech. That is a broadcast-style call, not a rep conversation and not an AI agent. Autocloz's in-browser dialer runs on Telnyx, DIDLogic and FreJun, so Vonage is not an option in the dialer.
What Vonage does not do in Autocloz
- No JWT signing from the stored private key.
- No browser softphone, inbound call webhook or recording import for Vonage. The voice platform page lists which carriers have them.
- Delivery and call outcomes need a relay to Autocloz's outcomes endpoint.
Troubleshooting Vonage
- Vonage returns 401 on calls or WhatsApp.
- The API key field holds a plain key, not a signed JWT. Voice and WhatsApp need the JWT.
- SMS fails with "api_key + api_secret + from_handle required".
- Fill in the API secret and a from-number on the card.
Part of the Call stack
Vonage is one of several carriers you can run behind the Call channel. They share the same dialer, CDR logging, recordings UI and compliance gates.
Explore the Call featureRelated integrations
Call Control v2 + WebRTC softphone, signed-URL recordings, Ed25519 webhook verification.
View integrationIn-browser Voice SDK calling + low international SIP rates; CDR poll for retroactive ingest.
View integrationIndia-native voice with per-agent OAuth, presence sync + recording import.
View integrationFrequently asked
Does Autocloz sign Vonage JWTs for me?
No, not today. The private key field is stored but not used for signing.
Does Vonage SMS work?
Yes, with the API key, secret and from-number on the card. See the Vonage SMS page.
Run Vonage inside Autocloz
Bring your own account, plug it into the Call channel, and keep a free-forever CRM for 3 users.