Identity and gating status for the current session

Answers for gated users: a waitlisted account gets 200 with status: "beta_required", never a 403. 401 means there is no valid session at all.

wallet is the authoritative binding for the session — one browser holds one session cookie, so a wallet switch in another tab rebinds it. Clients should revalidate this endpoint on focus/visibilitychange and discard cached per-wallet data when wallet changes.

Cookie sessions additionally receive their CSRF token in the X-CSRF-Token response header — echo it back on every POST/PUT/PATCH/DELETE. The token is derived from the session cookie, so call this endpoint again to recover from a rotated one.

get/auth/session

Response

Current session

idnumber required

DRE user id

walletstring required

Wallet address this session is bound to

rolesnumber[] required

Role ids held by the user

status'active' | 'profile_required' | 'beta_required' required

Which gate the user is behind. profile_required takes precedence over beta_required.

Identity and gating status for the current session

Response

Changes