Whenever you collect an email address it is best practice to verify that the person who provided it actually owns it. It's all part of getting email consent to send emails. The Email Verification API is a new proposal to
When a user enters an email address in a form online, it's common practice to verify their email by sending a one-time password (OTP) or magic link. The user leaves the webpage, opens their inbox, and copies a code or cl
The API has a few different parties involved: the user, the browser, the mailbox provider (known as the issuer), and your server (the verifier). Here's a quick and simple version of how it all works together: - The user
We'll start with the HTML form. The email needs to be of type "email" with the attribute set to "email" as well. You also need to provide a hidden input with the attribute of "email-verification-token" that has a random
The process of verifying the token is quite involved, requiring parsing, DNS and network lookups, and verifying the token signatures. If your server is written in JavaScript, I built an npm package to perform the verific
I really like this API for two reasons. For the user, there's no more heading off to their inbox to verify their email when they are just trying to get something done, and they don't have to change their behavior at all.
