What a business gets
Cascade WhatsApp OTP provides a server-side flow for verifying a user's phone number. You do not need separate generation, delivery, and verification logic for each product interface.
The core capability includes a six-digit code, five-minute expiration, API verification, delivery responses, optional short links, and company history and balance in the dashboard.
This is outbound delivery to your own customers. Cascade does not rent temporary numbers for signups on third-party services.
Suitable use cases
| Use case | What the code confirms |
|---|---|
| Signup | Control of the submitted number |
| Login | Access to the delivery channel |
| Recovery | A request to regain account access |
| Data change | Phone, email, or security setting update |
| Sensitive action | Confirmation inside your product |
| Short link | Access to an order, payment, or confirmation screen |
For high-risk operations, combine OTP with session checks, anti-fraud controls, or another factor.
Integration flow
The frontend calls your backend, and your backend calls Cascade. The Bearer token never enters browser or mobile code.
- The user enters a phone number.
- Your backend calls
POST /api/otp/sendwithchannel: whatsapp. - Cascade delivers the code and returns its expiration.
- The user enters the code in your interface.
- Your backend calls
POST /api/otp/verify. - Your product continues only after
success: true.
curl -X POST "https://cascade.kz/api/otp/send" \
-H "Authorization: Bearer $CASCADE_API_TOKEN" \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"phone":"77001234567","purpose":"login","channel":"whatsapp"}'
See the send reference and documentation for complete fields and responses.
WhatsApp OTP pricing
Successful WhatsApp delivery costs 3 credits, with no subscription fee. A new company receives 1000 starting credits for integration testing.
Before scaling, measure successful delivery, time to code entry, resend share, and credits per verified user—not only request volume. Current packages and billing rules are on pricing.
Code and short link together
The send endpoint accepts an optional link. Cascade creates a short URL and includes it with the code. This can return a user to an order, payment, or confirmation screen.
A link does not replace server-side risk checks. Set an expiration, validate destinations, and do not put sensitive data in the URL.
Limitations
- WhatsApp must be accessible to the recipient.
- Delivery depends on an external channel and cannot be guaranteed for every number.
- The API key must stay off the client.
- Send and verify require rate limits.
- The UI must handle code expiration and resend cooldown.
- Do not advertise SMS as active fallback; the public SMS provider is not live yet.
Products with different audience preferences can also use Telegram OTP through the same API.
Start a pilot
Create an account, obtain an API key, and test with consented internal phone numbers. Verify send, code validation, errors, countdown, and resend before enabling real user traffic.