Email Verification
Prove that a customer actually controls the email address they've submitted by sending and verifying a one-time password with a single token exchange.
Overview
What the Email OTP Authentication API does
FinHub's Email OTP Authentication API generates a time-bound one-time password, delivers it to the submitted address, and verifies the code the customer enters — confirming email ownership before it's trusted as an identifier or notification channel. Each OTP is bound to a consent token and every generate-verify pair is written to a tamper-evident audit log.
Inputs
- Email address
- Consent artifact ID
- OTP expiry window
Returns
- OTP delivery status
- Verification token
- Match result (on verify call)
- Attempt count
- Expiry timestamp
POST /v1/email/otp/send
How it works
Three steps to a verified result
Request the OTP
Send the email address with a consent artifact; FinHub generates and delivers a time-bound one-time password.
Customer enters the code
The customer submits the OTP through your interface, which you pass to our verify endpoint with the issued token.
Get an ownership confirmation
Receive a match result and attempt count in real time — sealed to your audit trail as proof of ownership.
Use cases
Where teams use Email OTP Authentication
- Confirming email ownership during account opening
- Two-factor authentication for customer logins
- Verifying email changes on existing accounts
- Securing password-reset and consent-withdrawal flows
FAQ
Email OTP Authentication API — FAQs
Common questions about FinHub's Email OTP Authentication API.
FinHub sends a time-bound one-time password to the submitted address and verifies the code the customer enters, proving they control that inbox.
More verification APIs
Explore related APIs
Ready to add Email OTP Authentication to your flow?
Book a demo and see the API return a verified result on your own test data in minutes.