OTP SMS

Verification codes that never keep users waiting

Stable, fast and secure delivery for one-time passwords. OTP traffic runs on its own priority lane — completely separate from bulk campaigns.

Get Started API Documentation

verify · otp

Enter your verification code

482913

Verified in 0.9 s

OTP verified

Priority lane

Built for login flows, not campaigns

A verification code is only useful within seconds. That's why OTP messages are processed in a dedicated high-priority queue and sent over routes selected specifically for verification traffic in each country.

Your integration stays trivial: send the code through the same REST API, and the platform recognises OTP traffic and handles prioritisation and templating automatically.

Dedicated priority queue — OTP never waits behind bulk traffic
Per-country OTP routes tuned for verification delivery
Message templates — you send only the code, the text stays consistent
Real-time delivery status per message
Same API and panel as bulk SMS — one account, one balance
Numeric-only messages are auto-detected as OTP — no separate endpoint, and OTP API access can be toggled per account.

For Developers

Send an OTP with one request

Send the numeric code as the message — the platform applies your OTP template and pushes it down the priority lane.

Dedicated OTP lane

Verification traffic is processed on a priority queue, separate from bulk sending.

Template protection

Your OTP text is defined once as a template; the API only carries the code. No accidental content changes.

Webhook reports

Delivery statuses are pushed to your system in real time.

API Documentation

send-otp

# Numeric-only message = OTP → priority lane + template
curl -X POST https://sms.uipapp.com/api/v1/hub/ \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "action": "send",
    "numbers": ["+905301234567"],
    "message": "482913"
  }'

→ 200 OK
{ "status": "success", "campaign_id": "17529..." }

FAQ

Frequently asked questions

How is OTP different from normal sending?+

OTP messages skip the bulk queue entirely and are processed with high priority, over routes selected for verification traffic. Your users receive their code within seconds.

How does the API know a message is an OTP?+

When OTP mode is enabled on your account, numeric-only messages sent to a small number of recipients are automatically treated as OTP: your template is applied and the message enters the priority lane.

Can I customise the OTP text?+

Yes. Your OTP template is defined on your account (per country if needed); the code is inserted into the template on every send. This keeps the wording consistent and prevents abuse.

Do I need a separate account for OTP?+

No — OTP and bulk SMS run on the same account, the same balance and the same API. We simply enable OTP mode and configure your template.