Auth0’s Management APIv2 now provides a means to validate emails from users logging in using any connection.
We added the option to specify a user identity when calling the following endpoints:
This jobs endpoint can be used when you want to leverage Auth0’s email templates to initiate an email verification flow. A new (optional) identity field can be specified in the payload. When specified, this will allow an email job to be created for a specific user identity within a user. The identity must include a provider and user_id.
If you prefer to leverage your own email capabilities, you can use this tickets endpoint to generate an email verification link to use in your custom flows. A new (optional) identity object field can be added to the payload. When specified, this will allow a ticket to be created for a specific user identity within a user. The identity must include a provider and user_id.
By doing this, you can select a secondary, federated, or passwordless-email identity to be verified. Once the user verifies their email using Auth0, the
email_verified flag associated with the provided identity will be set to
true. Subsequent logins using a federated identity will not overwrite this value. If the identity being verified happens to be the primary identity of the user, the
email_verified at the root of the user profile will also be set to true.
How does this affect me?
You can take advantage of this capability right away. If you choose not to specify an identity when initiating an email verification flow, no behavior will change. We will continue to only allow for verification of the primary identity of users belonging to the Auth0 IDP.
To explore these new capabilities, get started at: Email Verified Usage or explore the APIs