Use case
- Gate your app’s UI or navigation: Restrict access to application features that require authentication.
- Route authenticated members: Direct members with active sessions to your main application experience.
- Redirect unauthenticated members: Send members without sessions to your login or signup flow.
Retrieve a member session
Select a framework:- Next.js
- React
- Vanilla JS
Determine where to authenticate sessions in your application
We recommend placing this logic close to the entry point to each page you want to control in your application.
Implement useStytchMemberSession()
You can use the
useStytchMemberSession() hook to retrieve a member’s session data and listen for changes:Using the isInitialized and session values
The
useStytchMemberSession() hook returns the values:Whether or not the SDK has finished initializing. Ensure this is
true before checking for an active session.The active Member Session object.
null if there’s no active session.Whether the SDK is returning cached session data based on if the SDK has completed an Authenticate Session call or not.
For most cases, you can rely on checking the
session value as long as isInitialized is true.Using cached data and fromCache
The frontend SDK utilizes stale-while-revalidate (SWR) for faster time-to-interactivity and UX:
- The page first loads.
- Stytch’s SDK checks and returns cached Member and Session data to your application.
- The SDK refreshes Member and Session data in background session authentication while your application starts.
fromCache is false before checking the session value.