> ## Documentation Index
> Fetch the complete documentation index at: https://docs-dev-docs-event-stream-action-templates.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# EmailOtpChallenge
> Describes all the hooks and methods available to customize the Universal Login `email-otp-challenge` screen.
The `email-otp-challenge` screen is displayed when a user needs to verify their identity by entering a one-time passcode sent to their email address. It allows the user to submit the code or resend it.
## 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.
```jsx Import Example theme={null}
// root import
import { useEmailOTPChallenge } from '@auth0/auth0-acul-react';
// partial import
import {
useEmailOTPChallenge,
// Context hooks
useUser,
useTenant,
useBranding,
useClient,
useOrganization,
usePrompt,
useScreen,
useTransaction,
useUntrustedData,
// Common hooks
useCurrentScreen,
useAuth0Themes,
useErrors,
useResend,
// Utility hooks
useChangeLanguage,
// Methods
submitCode,
resendCode,
} from '@auth0/auth0-acul-react/email-otp-challenge';
function EmailOtpChallengeScreen() {
const { submitCode } = useEmailOTPChallenge();
return (
);
}
```
## Context Hooks
Screen-scoped hooks that provide read-only access to Auth0 context data on the `email-otp-challenge` screen. Import them from `@auth0/auth0-acul-react/email-otp-challenge`.
() => BrandingMembers}>
This hook provides branding configurations, such as logo, colors, and theme settings displayed on the `email-otp-challenge` screen.
```jsx Example theme={null}
import { useBranding } from '@auth0/auth0-acul-react/email-otp-challenge';
function CustomTheme() {
const branding = useBranding();
}
```
() => ClientMembers}>
This hook provides client-related configurations, such as `id`, `name`, and `logoUrl`, for the `email-otp-challenge` screen.
```jsx Example theme={null}
import { useClient } from '@auth0/auth0-acul-react/email-otp-challenge';
function AppInfo() {
const client = useClient();
}
```
() => OrganizationMembers}>
This hook provides information about the user's Organization if the OTP challenge is Organization-scoped. Returns `null` when no Organization context is present.
```jsx Example theme={null}
import { useOrganization } from '@auth0/auth0-acul-react/email-otp-challenge';
function OrgSelector() {
const organization = useOrganization();
if (!organization) {
return
No Organization context
;
}
}
```
() => PromptMembers}>
This hook contains data about the current prompt in the authentication flow.
```jsx Example theme={null}
import { usePrompt } from '@auth0/auth0-acul-react/email-otp-challenge';
function FlowInfo() {
const prompt = usePrompt();
}
```
() => ScreenMembersOnEmailOTPChallenge}>
This hook contains details specific to the `email-otp-challenge` screen, including its configuration and context.
```jsx Example theme={null}
import { useScreen } from '@auth0/auth0-acul-react/email-otp-challenge';
function ScreenDebug() {
const screen = useScreen();
}
```
() => TenantMembers}>
This hook contains data related to the tenant, such as `id` and associated metadata.
```jsx Example theme={null}
import { useTenant } from '@auth0/auth0-acul-react/email-otp-challenge';
function TenantInfo() {
const tenant = useTenant();
}
```
() => TransactionMembers}>
This hook provides transaction-specific data for the `email-otp-challenge` screen, such as active connections and current flow state.
```jsx Example theme={null}
import { useTransaction } from '@auth0/auth0-acul-react/email-otp-challenge';
function TransactionInfo() {
const transaction = useTransaction();
}
```
() => UntrustedDataMembers}>
This hook handles untrusted data passed to the screen, such as prefilled parameters from URL query strings.
```jsx Example theme={null}
import { useUntrustedData } from '@auth0/auth0-acul-react/email-otp-challenge';
function PrefilledForm() {
const untrustedData = useUntrustedData();
}
```
() => UserMembers}>
This hook provides details of the active user, including `username`, `email`, and available authentication methods.
```jsx Example theme={null}
import { useUser } from '@auth0/auth0-acul-react/email-otp-challenge';
function UserProfile() {
const user = useUser();
}
```
EmailOTPChallengeMembers}>
This hook returns all methods and context available on the `email-otp-challenge` screen.
## Methods
This method resends the one-time passcode to the user's email address.
```jsx Example theme={null}
import { useEmailOTPChallenge } from '@auth0/auth0-acul-react/email-otp-challenge';
function ResendButton() {
const { resendCode } = useEmailOTPChallenge();
return (
);
}
```
This method submits the one-time passcode entered by the user.
```jsx Example theme={null}
import { useEmailOTPChallenge } from '@auth0/auth0-acul-react/email-otp-challenge';
function SubmitButton() {
const { submitCode } = useEmailOTPChallenge();
return (
);
}
```
**Method Parameters**
[OtpCodeOptions](/docs/libraries/acul/react-sdk/API-Reference/Types/interfaces/OtpCodeOptions).
The OTP code entered by the user.
## Common/Utility Hooks
useAuth0Themes} type="Hooks">
This hook gets the current theme options with flattened configuration from branding context.
useChangeLanguage} type="Hooks">
This hook returns a function for changing the display language on the current ACUL screen.
useCurrentScreen} type="Hooks">
This hook gets the current screen context and state.
useErrors} type="Hooks">
This hook reads and manages server, client, and developer errors on the screen.
useResend} type="Hooks">
This hook manages resend state and cooldown logic for the email OTP code.
## 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.
```jsx Import Example theme={null}
// root import
import { useEmailOTPChallenge } from '@auth0/auth0-acul-react';
// partial import
import {
useEmailOTPChallenge,
// Context hooks
useUser,
useTenant,
useBranding,
useClient,
useOrganization,
usePrompt,
useScreen,
useTransaction,
useUntrustedData,
// Common hooks
useCurrentScreen,
useAuth0Themes,
useErrors,
useResend,
// Utility hooks
useChangeLanguage,
// Methods
submitCode,
resendCode,
} from '@auth0/auth0-acul-react/email-otp-challenge';
function EmailOtpChallengeScreen() {
const { submitCode } = useEmailOTPChallenge();
return (
);
}
```
## Context Hooks
Screen-scoped hooks that provide read-only access to Auth0 context data on the `email-otp-challenge` screen. Import them from `@auth0/auth0-acul-react/email-otp-challenge`.