Vonage · Nexmo
Vonage integration: SMS and voice
Vonage integration means your system uses Vonage to send SMS, run Verify codes or start calls, with webhooks on the result. It is a global telecom API. The same choice as [Twilio](/articles/integrations/twilio-integration): take it if you are already there, or if you have voice and SMS in the same product. For Danish SMS only: compare [GatewayAPI](/articles/integrations/gatewayapi-integration) first. One-time codes should use a Verify product or your own rate limit, expiry and lockout. A homemade “send 4 digits and store them in the session” is a support and security bill. Sender approved. Never a CPR number in the SMS body.
8 min read · Updated 28 August 2026
Nexmo lives in old briefs and in some logins. We map the API you have keys for. Plivo is another name in the same drawer. Automation that owns the event.
Verify as a product
One-time codes are not “an SMS with four digits”. They are rate limit, expiry, lockout, hash and a trail you can explain when someone asks why the account was locked.
- Use Vonage Verify or your own code layer with the same rules
- Do not store the code in the session in clear text
- Lock after N attempts. Tell the user why
- Log send-out and result, not the code itself
Event
Login, alarm or booking triggers one job.
Channel
SMS, Verify or voice — chosen in configuration.
Webhook
Result is written on the user. Retry is idempotent.
What to do now
Do you already have Vonage or Nexmo? Then we start there. Have none: say whether voice is in scope. Write what you log in with.
FAQ about Vonage integration
Is it Vonage or Nexmo in the quote?
Must Verify be Vonage’s product?
Vonage or Twilio for voice?
Danish SMS only — is Vonage first choice?
Want us to build it for you?
You get a fixed-price proposal within 24 hours.
