StytchClient

Exposes an instance of the Biometrics interface which provides methods for detecting biometric availability, registering, authenticating, and removing biometrics identifiers.

Exposes an instance of the CryptoWallet interface which provides methods for authenticating with a crypto wallet

Exposes an instance of the DFP interface which provides a method for retrieving a dfp_telemetry_id for use in DFP lookups on your backend server

Exposes a flow that reports the initialization state of the SDK. You can use this, or the optional callback in the configure() method, to know when the Stytch SDK has been fully initialized and is ready for use

Exposes an instance of the MagicLinks interface whicih provides methods for sending and authenticating users with Email Magic Links.

Exposes an instance of the OAuth interface which provides methods for authenticating a user via a native Google OneTap prompt or any of our supported third-party OAuth providers

Exposes an instance of the OTP interface which provides methods for sending and authenticating One-Time Passcodes (OTP) via SMS, WhatsApp, and Email.

Exposes an instance of the Passkeys interface which provides methods for registering and authenticating with Passkeys.

Exposes an instance of the Passwords interface which provides methods for authenticating, creating, resetting, and performing strength checks of passwords.

Exposes an instance of the Sessions interface which provides methods for authenticating, updating, or revoking sessions, and properties to retrieve the existing session token (opaque or JWT).

Exposes an instance of the TOTP interface which provides methods for creating, authenticating, and recovering TOTP codes

Exposes an instance of the UserManagement interface which provides methods for retrieving an authenticated user and deleting authentication factors from an authenticated user.

A helper function for determining whether the deeplink is intended for Stytch. Useful in contexts where your application makes use of a deeplink coordinator/manager which requires a synchronous determination of whether a given handler can handle a given URL.

This configures the API for authenticating requests and the encrypted storage helper for persisting session data across app launches. You must call this method before making any Stytch authentication requests.

Retrieve the most recently created PKCE code pair from the device, if available

Call this method to parse out and authenticate deeplinks that your application receives. The currently supported deeplink types are: Email Magic Links, Third-Party OAuth, and Password resets.

Retrieve the token and a concrete token type from a deeplink