Send OTP for login, registration, password reset, and payments. Two endpoints (send and verify), hashed codes that expire, JavaScript and PHP SDKs. Cheaper than SMS. Free 100 messages/month, paid from $1.
Your users live on WhatsApp. The OTP arrives where they are already active every day, opened far faster than SMS or email.
No varying per-carrier SMS rates. Verification costs are lower and easier to predict at scale.
Two endpoints: send OTP and verify. Drop it into PHP, Node.js, Laravel, and other stacks in minutes.
OTP codes are stored hashed and expire automatically, so they are safe for passwordless login and transaction verification.
# Send WhatsApp OTP
POST https://api.loginwa.com/api/v1/auth/start
{
"phone": "+6281234567890"
}
# Verify the code
POST https://api.loginwa.com/api/v1/auth/verify
{
"session_id": "...",
"otp_code": "123456"
}Sign up free, get your API key, and send your first OTP in minutes. Upgrade any time (instant QRIS for Indonesian payers).
Start freeA one-time code on WhatsApp. LoginWA: POST /api/v1/auth/start then POST /api/v1/auth/verify. Codes are hashed and expire.
Usually yes. WhatsApp OTP is not billed at varying per-carrier SMS rates, so costs are lower and more predictable, especially at high volume.
Just call the LoginWA API endpoint with the destination number, and the system sends the OTP code via WhatsApp. After the user enters the code, call the verify endpoint to validate it. You can integrate with PHP, Node.js, Laravel, and any other language that can make HTTP requests.
Yes. OTP codes are stored hashed and expire automatically after a set period, so they are secure for WhatsApp number verification and login.
Yes. Many LoginWA users use WhatsApp OTP for passwordless login, registration, password reset, and transaction verification.