How this workflow fits
Add verification where it matters
An OTP step can confirm access to a phone number during account creation, help recover an account, or approve a sensitive action. Decide which actions require verification and what your application should do after a successful or unsuccessful attempt.
- Explain why the customer is being asked to verify.
- Set an expiry period appropriate to the action.
- Apply limits to requests and validation attempts.
Choose a code or link flow
The request-code endpoint generates a code and queues it for delivery to the supplied WhatsApp or SMS chat ID. The generate-link endpoint creates a WhatsApp link for passwordless verification. Validate codes through the validation endpoint; handle link success and failure with the configured callbacks.
- Use codes when the user enters a value in your app.
- Use links when passwordless WhatsApp sign-in fits your flow.
- Keep credentials short-lived and out of application logs.
Keep authentication under your control
Hypersender provides OTP delivery and validation capabilities; your application remains responsible for account security, session creation, abuse controls, and user recovery. Review the endpoint requirements and test edge cases such as expired codes and repeated requests.
- Never treat message submission alone as successful verification.
- Choose WhatsApp or SMS deliberately for your integration.
- Automatic fallback between channels is not implied.