After five incorrect verification attempts, the code is locked and you must request a new one. The API returns the message "Too many incorrect attempts. Request a new code." You cannot retry the same code after reaching this limit.
More details arrow_forward
Each OTP is valid for five minutes from the moment it is sent. After that it expires and returns the error "This code has expired". The successful send response also includes expires_in: 300 so your app can count down.
More details arrow_forward
A successful verification returns verified: true in the JSON body. An incorrect code returns verified: false along with an error message. After five wrong attempts the response changes to the too-many-attempts error.
More details arrow_forward
Phone numbers must include the country code and contain digits only, with no plus sign, spaces, dashes or brackets. For example, an Indian number should be sent as 919876543210, not +91-98765-43210.
More details arrow_forward
The purpose field is an optional label attached to the OTP request for your own logs. Documented examples are login, signup and checkout. It does not affect how the OTP is sent or verified.
More details arrow_forward
No. OTP API requests should be made from server-side code only. Putting your API key in frontend JavaScript exposes it to anyone who views your page source, so all calls to the send and verify endpoints must go through your backend.
More details arrow_forward
POST to https://app.waloops.com/api/otp/send.php with a JSON body containing the phone field. Include the X-API-Key header with your key and, for non-WordPress apps, the X-Site-Url header with your application's public URL.
More details arrow_forward
POST to https://app.waloops.com/api/otp/verify.php with a JSON body containing phone and code. Use the same phone number that received the code, the same X-API-Key header, and X-Site-Url if you are not on WordPress.
More details arrow_forward
WALoops returns HTTP 400 when the phone number is missing or invalid. Make sure the number includes the country code and contains digits only before sending the request.
More details arrow_forward
The Starter OTP plan costs $9.99 or Rs 999 per month and includes unlimited OTPs sent from your own connected WhatsApp number, plus 3,000 monthly credits for OTPs sent from the WALoops number. One OTP from the WALoops number uses one credit.
More details arrow_forward
No. On the Free plan, OTPs are sent from the WALoops WhatsApp number and no Meta developer account or Business API setup is required on your side. You only need a WALoops API key.
More details arrow_forward
The WALoops OTP API supports any language that can make an HTTPS POST request with a JSON body. Official code examples are provided for cURL, PHP, Node.js and Python.
More details arrow_forward
The WALoops WordPress OTP Login plugin offers three form styles: Modern, Minimal and Card. You select the style in Settings > WhatsApp OTP Login inside your WordPress admin.
More details arrow_forward
Contact Form 7, WPForms, Gravity Forms and Formidable Forms support OTP verification fields through the plugin. Ninja Forms support is experimental and should be tested before relying on it. Elementor Pro Forms, Fluent Forms and SureForms are not supported.
More details arrow_forward
No. The plugin adds a separate WhatsApp OTP login option but does not replace or remove the site's existing username-and-password login form. Both methods remain available to users.
More details arrow_forward
Yes. The plugin can optionally send six-digit login codes by email without using the OTP API. Email-code OTPs are valid for 10 minutes and are single-use, compared to five minutes for WhatsApp OTPs.
More details arrow_forward
The WALoops OTP Login plugin requires WordPress 5.8 or later and PHP 7.4 or later. Check your hosting dashboard to confirm the versions running on your server before installing.
More details arrow_forward
Yes. When a user requests a code, the plugin sends their phone number to WALoops to dispatch the OTP. When they submit the code, the plugin also sends the phone number and code to WALoops for verification.
More details arrow_forward
After installing the WALoops OTP Login plugin, the settings are at Settings > WhatsApp OTP Login in your WordPress admin dashboard. That is where you paste your API key and choose the form style.
More details arrow_forward
No. Each OTP code can be used only once. After a successful verification the code is consumed and cannot be reused. You must request a new code for any subsequent login or verification.
More details arrow_forward
Send a POST request to https://app.waloops.com/api/otp/send.php. The endpoint accepts a JSON request body and requires an API key in the X-API-Key header.
More details arrow_forward
Send a POST request with JSON containing phone and code to https://app.waloops.com/api/otp/verify.php. Verification uses the same phone number that received the code.
More details arrow_forward
The send endpoint requires phone and also accepts an optional purpose label. Purpose values can describe login, signup or checkout activity in the logs.
More details arrow_forward
The phone number must include its country code and contain digits only. A missing or invalid phone number returns HTTP 400.
More details arrow_forward
The verify endpoint requires both phone and code in the JSON body. The phone must match the number that received the code.
More details arrow_forward
An OTP remains valid for five minutes. An expired code returns the error This code has expired.
More details arrow_forward
No. The same phone number can request a resend once every 30 seconds. A resend attempt made sooner returns HTTP 429.
More details arrow_forward
A code allows up to five incorrect verification attempts. After five failures, the response says Too many incorrect attempts. Request a new code.
More details arrow_forward
An incorrect code returns verified: false with an error message. The failed attempts count toward the five-attempt limit.
More details arrow_forward
A successful send response includes success: true and expires_in: 300. The value 300 indicates a five-minute validity period.
More details arrow_forward
A successful verification response includes verified: true. The same phone number and code used by the recipient are required.
More details arrow_forward
HTTP 400 indicates a missing or invalid phone number. Include a country code and digits only in the phone field.
More details arrow_forward
The Introduction OTP plan costs $5 or ₹499 per month and includes 1,000 OTPs per month.
More details arrow_forward
The Starter OTP plan costs $9.99 or ₹999 per month and includes unlimited OTPs on a connected number.
More details arrow_forward
The Starter plan includes 3,000 monthly credits for OTPs sent from the WALoops number. One OTP uses one credit.
More details arrow_forward
Yes. An Advance account API key can call the OTP API to send and verify codes.
More details arrow_forward
Keep the API key server-side and outside frontend code delivered to a browser. Make OTP API requests from server-side code, not browser code.
More details arrow_forward
No. If a recipient does not have WhatsApp, the WhatsApp OTP cannot be delivered to that number.
More details arrow_forward
No. The Free plan does not require the caller to set up Meta. It sends OTPs from the WALoops WhatsApp number.
More details arrow_forward
OTP messages use a Meta-approved authentication template. WALoops provides the approved template on the WALoops WhatsApp number.
More details arrow_forward
No. DLT registration is required for SMS in India, but not for WhatsApp OTP.
More details arrow_forward
WALoops supports cURL, PHP, Node.js and Python examples. Any language that can make an HTTPS POST request with JSON can call the API.
More details arrow_forward
Yes. The plugin can add OTP forms to WordPress login and registration pages.
More details arrow_forward
Use the [wa_otp_login] shortcode to place the OTP login form on a WordPress page.
More details arrow_forward
The plugin offers Modern, Minimal and Card form styles for its WhatsApp OTP form.
More details arrow_forward
Yes. It can optionally send six-digit login codes by email without using the WhatsApp OTP API.
More details arrow_forward
Email-code OTPs are valid for 10 minutes and can be used once.
More details arrow_forward
The plugin supports OTP verification fields in Contact Form 7, WPForms, Gravity Forms and Formidable Forms.
More details arrow_forward
Ninja Forms support is experimental and should be tested before relying on it.
More details arrow_forward
Elementor Pro Forms, Fluent Forms and SureForms are not supported by the OTP Login plugin.
More details arrow_forward
The plugin requires WordPress 5.8 or later and PHP 7.4 or later.
More details arrow_forward
No. The plugin does not replace the site's existing username-and-password login form. It adds OTP verification alongside the existing setup.
More details arrow_forward