Verify

OTP and 2FA over SMS, WhatsApp, and voice

The highest-intent CPaaS use case: prove a phone number at signup, login, and high-risk actions. One API instead of three vendors.

See API docs

const res = await fetch("https://api.converixai.com/v1/messages", {
  method: "POST",
  headers: {
    Authorization: "Bearer YOUR_API_KEY",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    channel: "sms",
    to: "+9198XXXXXXXX",
    from: "CONVRX",
    body: "Your OTP is 482193. Valid for 5 minutes.",
  }),
});

Built for authentication traffic

One Verify API

Start a verification, we send the code, you check it. SMS, WhatsApp, or voice — with automatic fallback.

Channel fallback

If SMS is delayed, retry on WhatsApp or a voice call so logins still complete.

Abuse controls

Rate limits, attempt caps, and configurable TTL so OTP isn’t a vector for SMS pumping.

India-ready

DLT templates for authentication traffic and alphanumeric sender IDs.

Voice OTP

Play the code as speech for users who don’t receive SMS.

Webhooks

Know when the code was delivered, failed, or converted.

Typical flow

01
POST /v1/verify/start with the user’s phone and preferred channel.
02
We deliver a time-bound code and fire delivery webhooks.
03
POST /v1/verify/check. On success, mark the session verified.

Works with banking, fintech, marketplaces, and healthcare logins
Pair with WhatsApp authentication templates where allowed
Usage billed per successful verification attempt — see pricing

Replace homegrown OTP

If you still concatenate SMS gateways and hope for the best, Verify is the product to start with.

Read the docs