-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
verify validity of emails before sending email verification code #5014
Comments
@divine-comedian, nice feature, if we want to hide API key we can hide also on FE side using server action, also maybe we can hide it on the BE side and add there additional function that will have validation of the email. All option are open, but my opinion is that on BE side we can use that function much more than on FE side. |
Interesting points @kkatusic Also considering for testing it locally and on staging would it be more accessible if it was wrapped in an impact-graph query? Would it have any considerable effect on back-end resources? would we need to consider any rate limiting? |
@divine-comedian on BE side we need to add helper function that will validate email with that service after that we need to add extra api route that FE can fetch and send email string to test. |
In the current email verification flow we do not check if the entered email address is valid and free from typos
when we attempt to send an email through Ortto, if the email is invalid it gets added to a supression list and the customer's profile is unsubscribed from all emails. This creates a backlog of user support issues since someone has to manually resubscribe the user if the user needs to correct their email and request a new code.
we should use an email verification service to ensure emails are valid before we send the back-end request to send the verification code.
Here's some free services that might meet our usage requirements:
free - unlimited usage
https://verifyright.co/api-docs
free - 25 free requests per day
https://verifalia.com/email-verification-api
should we put this in the front-end or wrap it in a query from the back-end to keep our api key hidden?
The text was updated successfully, but these errors were encountered: