Account

Logged in

Landing point after an identity provider sign in, which completes whatever flow was started before the redirect (connecting an additional login method, verifying an email address for one, or accepting a workspace invite) and returns where to send the User next together with whether a multi factor challenge is required. When the email address still needs to be verified, a VERIFY_EMAIL action and the verification hash are returned instead.

GET /api/sys/v{version:apiVersion}/account/logged_in

Authorisation: No authentication needed

Request arguments

Name	Type	Source

Request body example

No input arguments

Response

Status: 200 (OK)
Type: DTO_logged_in_response

Wrapper: DTO_response_wrap

Other statuses: 400 (BadRequest), 403 (Forbidden)

Response body example

DTO_logged_in_response

Name	Type	Description
challenge_mfa	Boolean	Challenge mfa
action	ENUM logged_in_response_action	Action
info_messages	String[]	Can contain for example "Joined tenant". "Auth method Google added"
warning_messages	String[]	Warning messages
redirect_url	String	Redirect url
verification_hash	String	Verification hash
email	String	Email

ENUM logged_in_response_action

Value	Name	Description
0	UNKNOWN	UNKNOWN
1	REDIRECT	REDIRECT
2	SELECT_TENANT	SELECT_TENANT
3	CREATE_TENANT	CREATE_TENANT
4	CONTINUE_TO_APP	CONTINUE_TO_APP
5	LOGIN	LOGIN
6	VERIFY_EMAIL	VERIFY_EMAIL

Generated Aug 4, 2026 18:37