Feature: Enhance the create user management API to obey “verify_email” for the passwordless “email” connection and add a “verify_phone_number” property that is followed for the passwordless “sms” connection.
Description: When creating a new user for a “email” connection and a body that looks like this:
{
“email”: “john.doe@gmail.com”,
“connection”: “sms”,
“verify_email”: false
}
An email is sent automatically. According to this post, it is not a verification email, however, when passing in a body like below, the email is not sent upon user creation.
{
“email”: “john.doe@gmail.com”,
“connection”: “sms”,
“email_verified”: true
}
The user creation under a “email” connection ignores the “verify_email” property, and ignores when the Verification Email Template is disabled. My current workaround is to create the user with “email_verified”:true, then immediately update the user to set “email_verified”:false, as described here.
Example screenshot of the received email is below.
When creating a new user for a “sms” connection, there is no option to prevent the initial SMS message from being sent to the user.
Use-case: We are doing a “silent registration” process for our customers during the initial interaction with our product. We want to create the user account for email and SMS connection, but do not want to require the user to “sign in” by verifying the code/link sent to them. It is only during a subsequent login that the user must enter the code sent to their email or phone. The automatic email/sms during user creation is a negative user experience that we want to control ourselves.