Build custom authentication UI using Para’s React hooks for simplified state management
This guide covers building custom authentication UI using Para’s React hooks from @getpara/react-sdk@alpha. This approach provides simplified state management and is recommended for most React applications.
For maximum control over authentication flow and custom React Query implementations, see the Para Client Approach.
There are three stages for an authenticating user and three corresponding AuthState types that are returned from various authentication methods:
Stage
Meaning
Applicable Methods
'verify'
The user has entered their email or phone number and been sent a confimation code via email or SMS. Alternatively, they have logged in via an external wallet and need to sign a message to verify their ownership of the wallet.
signUpOrLogIn, loginExternalWallet
'signup'
The user has verified their email, phone number, external wallet, or completed a third-party authentication and may now create a WebAuth passkey or password to secure their account.
You will most likely want to track the AuthState within your app and update it with each method resolution. For example, you may want to store it in a dedicated context:
To authenticate a user via email or phone number, use the useSignUpOrLogIn hook. This mutation will either fetch the user with the provided authentication method and return an AuthStateLogin object, or create a new user and return an AuthStateVerify object.
If the user already exists, you will need to open either the passkeyUrl or passwordUrl in a new window or tab, then invoke the useWaitForLogin mutation. This hook will wait until the user has completed the login process in the new window and then perform any needed setup.
If the user is new, you will then need to display a verification code input and later invoke the useVerifyNewAccount mutation.
While in the verify stage, you will need to display an input for a six-digit code and a callback that invokes the useVerifyNewAccount hook. This will validate the one-time code and, if successful, will return an AuthStateLogin object. (The email or phone number previously entered is now stored, and will not need to be resupplied.)
Copy
Ask AI
import { useVerifyNewAccount } from "@getpara/react-sdk@alpha";import { useAuthState } from '@/hooks';function VerifyOtp() { const { verifyNewAccount, isLoading, isError } = useVerifyNewAccount(); const [_, setAuthState] = useAuthState(); const [verificationCode, setVerificationCode] = useState(''); const onSubmit = (verificationCode: string) => { verifyNewAccount( { verificationCode }, { onSuccess: (authState) => { setAuthState(authState); const { isPasskeySupported, passkeyUrl, passwordUrl } = authState; // Update your UI and prepare to log in the user }, onError: (error) => { // Handle a mismatched code }, } ); }; // ...}
After verification is complete, you will receive an AuthStateSignup object. Depending on your configuration, the AuthStateSignup will contain a Para URL for creating a WebAuth biometric passkey, a Para URL for creating a new password, or both. For compatibility and security, you will most likely want to open these URLs in a new popup window, and then immediately invoke the useWaitForWalletCreation hook. This will wait for the user to complete signup and then create a new wallet for each wallet type you have configured in the Para Developer Portal. If you would like more control over the signup process, you can also call the useWaitForSignup hook, which will resolve after signup but bypass automatic wallet provisioning. To cancel the process in response to UI events, you can pass the isCanceled callback.
Depending on your configuration, the AuthStateLogin will contain a Para URL for creating a WebAuth biometric passkey, a Para URL for creating a new password, or both. For compatibility and security, you will most likely want to open these URLs in a new popup window, and then immediately invoke the useWaitForLogin hook. This will wait for the user to complete the login process and resolve when it is finished. To cancel the process in response to UI events, you can pass the isCanceled callback.
Para supports OAuth 2.0 sign-ins via Google, Apple, Facebook, Discord, and X, provided the linked account has an email address set. Once a valid email account is fetched, the process is identical to that for email authentication, simply bypassing the one-time code verification step. To implement OAuth flow, use the useVerifyOAuth hook.
Copy
Ask AI
import { type TOAuthMethod, useVerifyOAuth } from "@getpara/react-sdk@alpha";import { useAuthState } from '@/hooks';function OAuthLogin() { const popupWindow = React.useRef<Window | null>(null); const { verifyOAuth, isLoading, isError } = useVerifyOAuth(); const [authState, setAuthState] = useAuthState(); const onOAuthLogin = (method: TOAuthMethod) => { verifyOAuth( { method, onOAuthUrl: (popupUrl) => { popupWindow.current = window.open(popupUrl, 'ParaOAuth'); }, isCanceled: () => popupWindow.current?.closed, }, { onSuccess: (authState) => { setAuthState(authState); switch (authState.stage) { case 'signup': // New user: refer to 'Sign up a new user' break; case 'login': // Returning user: refer to 'Log in an existing user' break; }; }, onError: (error) => { // Handle a canceled OAuth verification }, } ); }; // ...}
To implement your own Telegram authentication flow, please refer to the official documentation. Para uses the following bots to handle authentication requests:
Once a Telegram authentication response is received, you can invoke the useVerifyTelegram hook to sign up or log in a user associated with the returned Telegram user ID. Users created via Telegram will not have an associated email address or phone number.
Copy
Ask AI
import { useVerifyTelegram } from "@getpara/react-sdk@alpha";import { useAuthState } from '@/hooks';type TelegramAuthObject = { auth_date: number; first_name?: string; hash: string; id: number; last_name?: string; photo_url?: string; username?: string;};function TelegramLogin() { const popupWindow = React.useRef<Window | null>(null); const { verifyTelegram, isLoading, isError } = useVerifyTelegram(); const [authState, setAuthState] = useAuthState(); const onTelegramResponse = (response: TelegramAuthObject) => { verifyTelegram( { telegramAuthObject: response }, { onSuccess: (authState) => { setAuthState(authState); switch (authState.stage) { case 'signup': // New user: refer to 'Sign up a new user' break; case 'login': // Returning user: refer to 'Log in an existing user' break; }; }, onError: (error) => { // Handle a failed Telegram verification }, } ); }; // ...}
Refer to the official documentation for information on Farcaster’s SIWF (Sign In with Farcaster) feature.
To use this authentication method, use the useVerifyFarcaster hook. The hook will supply a Farcaster Connect URI, which should be displayed to your users as a QR code. Like with Telegram, users created via Farcaster will not have an associated email address or phone number.
Copy
Ask AI
import { useVerifyFarcaster } from "@getpara/react-sdk@alpha";import { useAuthState } from '@/hooks';function FarcasterLogin() { const { verifyFarcaster, isLoading, isError } = useVerifyFarcaster(); const [authState, setAuthState] = useAuthState(); const [farcasterConnectUri, setFarcasterConnectUri] = useState<string | null>(null); const isCanceled = React.useRef(false); useEffect(() => { isCanceled.current = !farcasterConnectUri; }, [farcasterConnectUri]); const onClickCancelButton = () => { setFarcasterConnectUri(null); } const onClickFarcasterLoginButton = () => { verifyFarcaster( { onConnectUri: connectUri => { setFarcasterConnectUri(connectUri); }, isCanceled: () => isCanceled.current, }, { onSuccess: (authState) => { setAuthState(authState); switch (authState.stage) { case 'signup': // New user: refer to 'Sign up a new user' break; case 'login': // Returning user: refer to 'Log in an existing user' break; }; }, onError: (error) => { // Handle a failed Telegram verification }, } ); }; // ...}
Para supports two-factor authentication via one-time codes in Google Authenticator or similar apps. To check a user’s current 2FA status, use the useSetup2fa hook:
If the user has already set up two-factor authentication, the setup2fa mutation will return { isSetup: true }.
If not, the mutation will return { isSetup: false, uri: string }, where uri is a URI that can be scanned as a QR code by Authenticator or a similar app.
When the user has entered the code from their authenticator app, you can use the useEnable2fa hook to activate 2FA for their account.
Subsequently, you can use the useVerify2fa hook to verify the user’s account by their one-time code.
Copy
Ask AI
import { useSetup2fa } from '@getpara/react-sdk';function Setup2fa() { const { setup2fa, isPending } = useSetup2fa(); const [twoFAUri, setTwoFAUri] = useState<string | null>(null); const onClickSetup2fa = () => { setup2fa( undefined, { onSuccess: (result) => { if (result.isSetup) { // User has already set up 2FA } else { // Display QR code with result.uri setTwoFAUri(result.uri); } }, onError: (error) => { // Handle error }, } ); }; // ...}
To sign out the current user, use the useLogout hook. By default, signing out will preserve any pre-generated wallets (including guest login wallets) present in the device storage, some of which may not belong to the signed-in user. To clear all wallets, set the clearPregenWallets parameter to true.