Your API key is on the Settings > Account page, in the card labeled WhatsApp OTP Login (WordPress). If you signed up on the WordPress OTP plan, it appears on the Dashboard instead, in the same card.
More details arrow_forward
From your WordPress admin, install the WALoops OTP Login plugin, open Settings > WhatsApp OTP Login and click Get Free API Key, then enter your email and WhatsApp number. The key is returned instantly and the account is created with 100 free OTPs a month, no credit card needed.
More details arrow_forward
POST to /api/otp/send.php with your phone number, X-API-Key header and X-Site-Url header to send the code. Then POST to /api/otp/verify.php with the same headers, the phone number and the code the user typed; it returns {"verified": true} on a match.
More details arrow_forward
Yes. An Advance plan account API key can send OTPs and use the full set of account tools in the WALoops MCP server, in addition to all the OTP endpoints available on standalone OTP plans.
More details arrow_forward
For WordPress OTP Login plans, the API key is on the Dashboard in the WhatsApp OTP Login (WordPress) card.
More details arrow_forward
For other plans, find the API key under Settings > Account in the WhatsApp OTP Login (WordPress) card.
More details arrow_forward
Install WALoops OTP Login, open Settings > WhatsApp OTP Login, and click Get Free API Key. Enter your email and WhatsApp number; the key is returned instantly and a generated password is emailed to you.
More details arrow_forward
Look for the card titled WhatsApp OTP Login (WordPress), on the Dashboard for WordPress OTP Login plans or under Settings > Account for other plans.
More details arrow_forward
Yes. The key card has a Copy button, and its label changes to Copied after you copy the key.
More details arrow_forward
The provided Dashboard and Settings key-card details show a Copy button, but no API-key regeneration control or procedure.
More details arrow_forward
Yes. The same API key works with the WALoops OTP API and the WordPress plugin.
More details arrow_forward
An API key from a WALoops Advance account can send OTPs and use full account tools in the MCP server.
More details arrow_forward
No. Keep the API key on your server, not in frontend code sent to a browser.
More details arrow_forward
The WALoops API guide shows storing the key in an environment variable named WALOOPS_API_KEY.
More details arrow_forward
The REST API base URL is https://app.waloops.com/api/otp.
More details arrow_forward
Send JSON with the Content-Type: application/json header.
More details arrow_forward
Send the country code followed by the phone number digits, such as 919876543210.
More details arrow_forward
Yes. The send request accepts an optional purpose label, with examples including login, signup, and checkout.
More details arrow_forward
The send endpoint defaults the purpose to login when it is omitted or blank.
More details arrow_forward
Yes. The optional channel field defaults to WhatsApp; setting it to sms sends through Twilio.
More details arrow_forward
The optional channel field defaults to WhatsApp.
More details arrow_forward
Yes. The send request accepts an optional template_variant, which defaults to expiry.
More details arrow_forward
Yes. An authenticated server-side caller can set include_code to receive the generated code in the send response.
More details arrow_forward
No. The send endpoint warns not to pass a response containing the generated code directly to a browser.
More details arrow_forward
The documented successful response includes success: true and expires_in: 300.
More details arrow_forward
A WALoops OTP is a six-digit code.
More details arrow_forward
Yes. The verify request requires the same phone number that received the code, along with the code itself.
More details arrow_forward
The verify endpoint returns HTTP 400 with the message "phone" and "code" are both required if either field is missing or empty.
More details arrow_forward
The documented incorrect-code response is {"verified": false, "error": "Incorrect code"}.
More details arrow_forward
The documented error message for an expired code is “This code has expired.”
More details arrow_forward
After five wrong attempts, the documented error is “Too many incorrect attempts. Request a new code.”
More details arrow_forward
The documented response when the resend limit is hit is HTTP 429.
More details arrow_forward
The documented response is HTTP 429 with the plan limit.
More details arrow_forward
The API page documents HTTP 400 for missing or invalid phone numbers.
More details arrow_forward
The send endpoint requires POST; another method returns HTTP 405 with “Method not allowed.”
More details arrow_forward
No. The verify endpoint requires POST; another method returns HTTP 405 with “Method not allowed.”
More details arrow_forward
Introduction includes 1,000 OTPs per month. Starter is an unlimited-OTP plan when sending from your own WhatsApp number after Meta approves it.
More details arrow_forward
Yes. Introduction can use the WALoops number or a connected WhatsApp Business number.
More details arrow_forward
Starter has no WALoops OTP limit for sends from your own WhatsApp number once Meta approves it.
More details arrow_forward
Starter includes 3,000 credits per month for sends from the WALoops number, with one credit per OTP.
More details arrow_forward
Meta bills authentication messages sent from your own number to your WhatsApp Business account at Meta’s rate.
More details arrow_forward