email-identifier-challenge screen is displayed when a user needs to verify their identity by entering a code sent to their email address. It allows the user to submit the code, resend it, or return to the previous step.

Import
Each screen has its own set of hooks and methods. The SDK supports partial import and root import for each screen.- Using partial import allows you to include only the code you need for your specific use case.
- Using root import allows you to load all screens from a single bundle, which is useful when you want a unified build to handle all possible screens.
Import Example
Context Hooks
Screen-scoped hooks that provide read-only access to Auth0 context data on theemail-identifier-challenge screen. Import them from @auth0/auth0-acul-react/email-identifier-challenge.
() => BrandingMembers
This hook provides branding configurations, such as logo, colors, and theme settings displayed on the
email-identifier-challenge screen.Example
() => ClientMembers
This hook provides client-related configurations, such as
id, name, and logoUrl, for the email-identifier-challenge screen.Example
() => OrganizationMembers
This hook provides information about the user’s Organization if the email challenge is Organization-scoped. Returns
null when no Organization context is present.Example
() => PromptMembers
This hook contains data about the current prompt in the authentication flow.
Example
This hook contains details specific to the
email-identifier-challenge screen, including its configuration and context.Example
() => TenantMembers
This hook contains data related to the tenant, such as
id and associated metadata.Example
() => TransactionMembers
This hook provides transaction-specific data for the
email-identifier-challenge screen, such as active connections and current flow state.Example
() => UntrustedDataMembers
This hook handles untrusted data passed to the screen, such as prefilled parameters from URL query strings.
Example
() => UserMembers
This hook provides details of the active user, including
username, email, and available authentication methods.Example
This hook returns all methods and context available on the
email-identifier-challenge screen.Methods
Promise<void>
This method resends the verification code to the user’s email address.
Example
Promise<void>
This method navigates the user back to the previous step in the authentication flow.
Example
Promise<void>
This method switches the authentication flow from email OTP verification to password-based authentication.
Example
Promise<void>
This method submits the email verification code entered by the user.Method Parameters
Example
Common/Utility Hooks
Hooks
This hook gets the current theme options with flattened configuration from branding context.
Hooks
This hook returns a function for changing the display language on the current ACUL screen.
Hooks
This hook gets the current screen context and state.
Hooks
This hook reads and manages server, client, and developer errors on the screen.
Hooks
This hook manages resend state and cooldown logic for the email verification code.