Authorizations
After a user logs in successfully, a session is created and a JWT token is returned.
This token represents the user's authenticated session.
It must be included in the Authorization
header as a Bearer token for all protected endpoints:
Authorization: Bearer <your-token>
The server will validate this token to authorize access.
Body
application/json
Available options:
login-explicit-abort
, login-error
, login-error-untyped
, login-error-unexpected
, login-one-tap-switch
, login-no-credentials
, user-append-after-cross-platform-blacklisted
, user-append-after-login-error-blacklisted
, append-credential-exists
, append-explicit-abort
, append-error
, append-error-unexpected
, append-learn-more
, manage-error-unexpected
, manage-error
, manage-learn-more
, manage-credential-exists
, local-unlock
Response
204
tbd