universal_login_context for this screen (window.universal_login_context) will contain:
client: Information about the Auth0 application.organization(optional): Details if the authentication is for a specific organization.prompt: Context of the current authentication prompt (e.g., ‘login’).screen: UI texts and general screen information. No screen-specificdatafields are uniquely defined forlogin-email-verificationbeyond standard ones.transaction: Details of the ongoing transaction, including state and any errors from previous attempts (e.g., “invalid-code”).
Example
Properties
branding
client
organization
prompt
screen
tenant
transaction
untrustedData
user
Methods
Submits the email verification code entered by the user.
This action corresponds to the user entering the code they received via email and
clicking a “Continue” or “Verify” button. The SDK will then POST this code
to the Auth0
/u/login-email-verification endpoint.If the code is valid, Auth0 will typically redirect the user to the next step in the
authentication flow. If the code is invalid, expired, or another error occurs,
Auth0 will usually re-render the login-email-verification screen, and the
transaction.errors array in the SDK’s context will be updated with details
about the failure (e.g., error code invalid-code).A promise that resolves when the form submission is initiated.
It does not return data directly upon resolution, as a redirect or
page re-render is the common outcome.Throws
Throws an error ifpayload.code is not provided or is not a string,
or if the FormHandler encounters an unrecoverable issue during submission (e.g., network error).
Validation errors from Auth0 (like an invalid code) are not thrown as JavaScript errors
but are reflected in this.transaction.errors after the operation.Example
Requests a new verification code to be sent to the user’s email address.
This action is typically invoked when the user clicks a “Resend Code” button, perhaps because
they didn’t receive the first email, the code expired, or they suspect an issue.
The SDK will POST to the Auth0
/u/login-email-verification endpoint with an action indicating
a resend request.Upon successful submission of this request, Auth0 attempts to send a new email.
The page may re-render. If there are issues (e.g., too many resend attempts for the same email,
identified by error code too-many-emails), transaction.errors will be updated.A promise that resolves when the resend request is initiated.
Like continueWithCode, this usually results in a page re-render or state update
rather than direct data in the promise resolution.Throws
Throws if theFormHandler encounters an unrecoverable issue (e.g., network error).
Server-side errors (like rate limits) are reflected in this.transaction.errors.Example
resendManager
Gets resend functionality with timeout management for this screen