BroadNet OTP delivers one-time passcodes to 200+ countries, direct to the operator in 86, with a sub-five-second median, automatic fallback across SMS, voice, WhatsApp and email, and HLR pre-validation on every send.
OTP traffic rides a path tuned for speed, not raw throughput — premium operator-direct binds, aggressive fast-fail timeouts, and multi-channel fallback wired into the same API.
Destination, intent, language. Retries inside the 5-min window return the same code, so duplicate submits never double-send.
Live HLR lookup catches disconnected, ported, and out-of-service MSISDNs. Velocity and IP-reputation score gates pumping attacks.
Premium direct binds reserved for authentication traffic. Aggressive fast-fail timeout drops slow operator paths instantly.
Sender ID rotation per destination. If no DLR in window, voice-TTS fallback fires automatically — same API, no re-integration.
Constant-time comparison defeats timing oracles. On success the verification context is purged from storage immediately.
Destination, intent, language. Retries inside the 5-min window return the same code, so duplicate submits never double-send.
Live HLR lookup catches disconnected, ported, and out-of-service MSISDNs. Velocity and IP-reputation score gates pumping attacks.
Premium direct binds reserved for authentication traffic. Aggressive fast-fail timeout drops slow operator paths instantly.
Sender ID rotation per destination. If no DLR in window, voice-TTS fallback fires automatically — same API, no re-integration.
Constant-time comparison defeats timing oracles. On success the verification context is purged from storage immediately.
One HTTPS call to POST /sms/sendSms — a Bearer token, a sender ID, the destination number and the code text. Use messageType TEXT for GSM or UNICODE for an Arabic code, and the response returns the message ID you reconcile against the delivery report.
curl -X POST https://api.broadnet.me/sms/sendSms \ -H "Authorization: Bearer $BROADNET_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "senderId": "BroadNet", "destinationNumber": "447700900123", "message": "Your verification code is 482913", "messageType": "TEXT" }' # 200 OK → response body is the message ID, e.g. 2603121407537573731You hit one endpoint. The platform handles validation, routing, escalation, fraud control, and cleanup so your verification flow stays a single line of code.
OTP traffic is segregated onto premium direct routes optimised for latency, not throughput. Aggressive timeouts drop a slow operator path within seconds rather than waiting for completion.
If the SMS leg doesn't return a delivery receipt within your configured window, the platform escalates to a voice call that reads the code aloud — no integration change required.
Per-country sender ID pools rotate automatically to avoid operator throttling and grey-route blacklisting. Registered alphanumerics are prioritised where regulation permits.
Inline Home Location Register lookups filter disconnected, ported, and out-of-service numbers before the OTP is dispatched. Invalid destinations return an immediate API error instead of billing waste.
Every request is scored against velocity, geography, IP reputation and historical patterns. Premium-rate toll-fraud destinations and signup-pumping bursts are blocked before they touch the network.
Codes self-expire and the verification context is purged from storage on use or timeout. Nothing personal lingers in logs longer than the audit window your compliance team set.
POST /sms/sendSms with the destination number and the code in the message text. Number validation can run first via /sms/lookup.
Fraud score, country policy and live route quality pick the optimal direct operator path.
Code is dispatched on the chosen sender ID. Carrier DLR streamed back over the same connection.
User enters the code; your app confirms in constant time and purges the context.
Drop-in verification widgets for web and mobile, a self-service dashboard, per-app code rules, and a free tier — built on the same OTP delivery path described on this page.
See MyOTP.App
The direct operator network your authentication traffic inherits as a BroadNet customer — the same interconnects that have carried messaging for Google, Meta, and Uber since 2003.
Reach for authentication traffic worldwide, direct to the operator in 86.
Direct operator interconnects; a labelled partner route where no direct bind exists.
Businesses that route messaging through BroadNet.
Two decades of carrier-grade delivery behind every OTP.
Every OTP carries an event trail you can replay on demand. Retention windows and residency are configurable per workspace.
OTP traffic is segregated onto premium operator-direct routes tuned for speed rather than raw throughput, so codes typically arrive before the user can reach for the resend button — fastest on direct MENA routes, with the global network close behind. If an SMS times out, voice fallback fires automatically, usually faster than the user retries.
No. You enable it once per channel in the dashboard and set the timeout window (default 10s); if the SMS DLR doesn't arrive in time, the voice leg is triggered for the same send. Your POST /sms/sendSms request stays exactly the same.
Three layers: velocity caps per MSISDN and per source IP, geo allow/deny lists per account, and a destination-prefix risk score that down-weights known toll-fraud ranges. Premium-rate prefixes in Eastern Europe, Africa, and parts of Asia are blocked by default; you whitelist what you legitimately need.
Per-delivery, per-country. UAE and KSA OTP traffic is $0.045–0.06/code on standard tier; voice fallback bills at $0.018/connected call. Sustained 5M+ codes/month qualifies for enterprise tiers in the $0.022–0.035 range. HLR pre-validation is included; it actually saves money by not sending to dead numbers.
TTL is configurable from 1 to 60 minutes; default is 5. On verify success, the entire context — code, MSISDN, intent — is purged from hot storage immediately. The audit trail (without the plaintext code) is retained 12 months on standard, 7 years on enterprise.
This product is SMS and Voice OTP. For TOTP/HOTP and silent network verification, see /products/myotp — same routing layer underneath, different verification primitives. Most customers run both, with SMS/Voice as the fallback when the device-based methods aren't available.
Sender ID pools rotate automatically and our regulatory team re-registers when rules change. The 2024 TDRA OTP-specific sender ID overhaul, for example, was handled in our backend in the grace window — customers didn't need to touch their integration. You'll see a dashboard note when a rotation happens; that's it.
The platform carries a 99.99% uptime SLA. OTP traffic runs on premium operator-direct routes across MENA (UAE, KSA, Egypt, Qatar, Bahrain, Kuwait, Oman, Jordan) with global reach beyond. Delivery targets, monitoring and any service credits are set in your commercial agreement, and an SLA report ships with every monthly invoice.
Question not here? Ask our engineering team
OTP delivery is one channel of BroadNet's A2P SMS platform. Teams often combine it with two-way SMS for reply-based verification, or the WhatsApp Business API for authentication conversations.
Comparing vendors? Read our Best OTP provider buyer's guide.
No grey routes: a direct operator bind wherever one is commercially available, otherwise a labelled partner-managed route. One API to every channel, on a network built since 2003.
One API call, six things handled, operator-direct routing. Talk to an engineer about volumes, country mix, or moving traffic over from your current provider.
Cost per completed verification
Resends, fallback and fraud change what each sign-in really costs. Model yours.
Further reading
Where the CAMARA network APIs are live, and how to check for a SIM swap before you send an OTP.
No, SMS OTP is not banned. What the CBUAE, RBI and BSP rules require of banks in 2026, who is in scope, the deadlines and what replaces SMS codes.
Resources
OTP datasheet
Go deeper on the concepts behind this product.