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.

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.

  1. Use Vonage Verify or your own code layer with the same rules
  2. Do not store the code in the session in clear text
  3. Lock after N attempts. Tell the user why
  4. Log send-out and result, not the code itself
SMS · transaktion
Din tekniker er 20 min. væk.
leveret
The code is short-lived. Status lands with you, not only at Vonage.
1

Event

Login, alarm or booking triggers one job.

2

Channel

SMS, Verify or voice — chosen in configuration.

3

Webhook

Result is written on the user. Retry is idempotent.

SMS, verify or call — one telecom layer

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?

In the docs: the name your login still uses. In your UI: SMS and calls, not the vendor logo.

Must Verify be Vonage’s product?

No. It must be a product with expiry and lockout. Vonage Verify is one way. Your own layer is another.

Vonage or Twilio for voice?

The one you have an account with. Two voice APIs in the same SME is a project we should talk you out of.

Danish SMS only — is Vonage first choice?

Rarely. Compare GatewayAPI on price and delivery unless you are already on Vonage.

Verify and SMS without a homemade code