Send and check one-time codes over WhatsApp, SMS and email from a single endpoint — with automatic fallback so a code still lands when a channel doesn't. Built for teams that outgrew a one-channel OTP box.
# request { "channel": "whatsapp", "to": "+91 98765 43210", "template": "login_code" } # 200 OK { "otp_id": "otp_8Kq2…", "channel": "whatsapp", "expires_in": 300 }
Set a channel order and Truspond escalates on its own — WhatsApp → SMS → email — so a failed or slow channel never means a locked-out user.
Stop stitching together three vendors. A single endpoint, one set of docs, one dashboard — WhatsApp, SMS and email behind it.
Delivery, success rate and time-to-verify per channel — so you can tune the order to what actually works for your users.
POST /v1/otp/send with a channel, a number or email, and (for WhatsApp/SMS) your approved template. You get back an otp_id.
POST /v1/otp/verify with the otp_id and what the user typed. You get back verified: true or a clear reason.
Prefer no-code? Truspond's hosted verify flow escalates WhatsApp → SMS → email on its own — you don't orchestrate a thing. See Verify →
Every call is authenticated with your secret key (Authorization: Bearer …), rate-limited per account, and you can subscribe to delivery & result webhooks so your backend hears the outcome without polling.
You choose the order per use-case — authentication, high-value logins, or password resets. Truspond handles the escalation and only ever charges for the channel that sent.
Dashboards for delivery and success rates, with uptime and response-time targets for teams that need them.
Verification results can flow into the same Truspond inbox and contact record your team uses — every contact carries a ✓ verified Trust badge.
Data protection by design, WhatsApp authentication templates and India DLT handled, built on Vibhum IT's engineering.
Verify email addresses at negligible cost — great for a first factor or a fallback.
You only pay for the channel that actually sent the code, at transparent per-message credit rates.
Committed volume plans, dedicated support and SLAs for larger teams — talk to us for a quote.
WhatsApp, SMS and email from a single endpoint. You can set a channel order and Truspond will fall back automatically — for example WhatsApp first, then SMS, then email — so a code still lands if the first channel fails.
Most OTP providers give you one channel per integration. Truspond gives you three channels behind one API with automatic fallback, plus delivery analytics and the option to sync verification results into the same inbox and CRM your team already uses. It is about reliability and unification, not being the cheapest per message.
WhatsApp verification uses an approved authentication-category template on your WhatsApp Business account, and SMS in India needs DLT registration. Email works out of the box. Truspond helps set up the template and DLT during onboarding.
Verification runs on prepaid credits priced by channel — email is effectively free, while WhatsApp and SMS consume credits because those channels cost money to send. Volume plans and SLAs are available for larger teams.
Get API access, or talk to us about volume, fallback rules and SLAs. Just want no-code order updates and OTPs? See Updates & OTP. Credit rates live on pricing.