Start with the right identifier
Ask for the email address or phone number associated with the account. Return consistent responses so the flow does not reveal which accounts exist.
Let people sign in with a code sent to their chosen channel. Keep verification, account lookup, and session creation separate so every step has a clear responsibility.
Ask for the email address or phone number associated with the account. Return consistent responses so the flow does not reveal which accounts exist.
Perform verification on your backend. Only create the authenticated session after success and bind the result to the intended user and action.
OTP is not phishing-resistant. For privileged access or high-risk transactions, assess passkeys, additional factors, and step-up authentication alongside your login flow.
Create an application, configure a channel, and connect from your backend. Review the API reference for complete request and response details.
curl -X POST 'https://api.otpwire.com/api/sdk/v1/sendOTP' \
-H 'X-API-Key: YOUR_SERVER_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"channel": "email",
"recipient": "[email protected]",
"purpose": "login",
"number_of_digits": 6,
"otp_format": "numeric",
"expiry_seconds": 300,
"locale": "en"
}'Bring WhatsApp and email verification into your product. We’ll help you find the right starting point.