Verify API
Email OTP
Verify users by delivering one-time passwords via email, an ideal fallback or primary channel for user onboarding and sensitive operations.
Free trialNo credit card requiredWhy Email OTP?
Cost-efficient
Email typically costs less per delivery vs SMS in many markets.
Preferred by users
Many users routinely check email, making it a seamless channel.
Fallback resilience
Email OTP can act as a backup if SMS or messaging channels fail.
How It Works
User provides email
The user enters their email address during flows like sign-up, password reset, or payment configuration.
Generate OTP
Your backend calls Dexatel’s Verify API with channel = "email_otp". Dexatel generates a random code valid for a limited time.
Send OTP email
Dexatel dispatches the OTP via email using your configured template. If the email fails, fallback logic can trigger alternate channels.
User submits OTP
The user enters the code in your user interface. This can be your web or mobile application.
Validate OTP
Your app calls the “verify/check” endpoint. Dexatel confirms whether the code is valid, unexpired, unused, and correct.
Complete the flow
You allow account creation, password reset, or transaction authorization. Otherwise, you present an error, allow a retry, or require reissuance.
What You Get With Email OTP
Configurable Code & TTL
Intelligent Fallback
Delivery Tracking
One-Time Use Codes
Pay-as-You-Go Pricing
Example API Usage
Send OTP via Email
Trigger Dexatel’s Verify API with channel = "email_otp" to send a secure one-time code to the user’s email. Used for sign-ups, password resets, or sensitive actions.
Email OTP Delivery Response
A 201 Created response confirms successful delivery. The response includes message_id, account_id, and OTP validity timestamps for tracking.
Verify Submitted OTP
After the user enters the code, call the Verify API check endpoint. Dexatel confirms if the OTP is correct, unexpired, and unused.
Successful Verification Response
Confirms the OTP is valid and verification is complete. Proceed with account creation, password reset, or transaction approval.
Use Cases and Scenarios
New User Registration
Verify that the provided email is valid before creating an account
Password Recovery/Reset
Send OTP to email to prove ownership of the account
Sensitive Transactions
Double confirmation via email OTP before critical actions
Email Change Verification
Confirm via OTP when a user updates their email
Login via Email
Send an OTP for a passwordless email login process.
Comparison With Other Channels
| Factor | Email OTP | SMS OTP | WhatsApp/Viber OTP |
|---|---|---|---|
Net Dependence | None | High | Medium (if user offline) |
Cost per delivery | Low | Higher | Varies |
Delivery speed | Fast | Very fast | Fast, with richer media |
Bounce/undeliverable | Moderate | Lower (carrier routing) | Depends on connectivity |
Fallback importance | Crucial (if email fails) | Useful (if SMS fails) | Useful (if messaging fails) |
Rich media/CTA | Basic (HTML email) | Very limited | Rich (buttons, images…) |
User familiarity | High | High | High |
Transparent and Flexible Pricing
| Channel | Price |
|---|---|
$0.0015 per email |
Start verifying users instantly with transparent, pay-as-you-go pricing.
Got Questions? We’ve Got Answers
Is Email OTP enabled by default?
It may be optional in your account. Contact Dexatel support to enable the email channel if needed.
Can I use email OTP and SMS fallback in one API call?
Yes. Configure fallback logic so that if email fails, the OTP is sent via SMS (or other approved channel).
Are OTP codes reused?
No. Each OTP is single-use and expires after the configured TTL or upon successful verification.
Does Dexatel guarantee delivery?
While we use a reliable email delivery infrastructure, external factors (spam filters, mailbox full, email domain issues) can affect deliverability. Dexatel provides delivery analytics so you can detect issues.
Get Started Today
Create your Dexatel account today and start verifying users via email.
