Passwordless
Overview
This page contains the APIs that are used to authenticate users without passwords using magic links and codes.
You also may find the Magic Links guide helpful.
Prior to version 1.41.0, magic links and codes were the only form of passwordless authentication supported by FusionAuth.
Therefore the user interface and API use the term passwordless, even though versions 1.41.0 and beyond support multiple kinds of passwordless authentication.
Start Passwordless Login
This API has been available since 1.11.0
This API allows you to generate a passwordless code that can be used to complete login. This is the first step in completing a passwordless login.
If you plan to utilize the FusionAuth login page then you will not need to use this API. Instead, once passwordless authentication is enabled for the FusionAuth Application, a new button will be presented to the user on the login page which will allow them to request an email.
Request
Request Headers
X-FusionAuth-TenantIdStringThe unique Id of the tenant used to scope this API request.
The tenant Id is not required on this request even when more than one tenant has been configured because the tenant can be identified based upon the request parameters or it is otherwise not required.
Specify a tenant Id on this request when you want to ensure the request is scoped to a specific tenant. The tenant Id may be provided through this header or by using a tenant locked API key to achieve the same result.
See Making an API request using a Tenant Id for additional information.
Request Body
applicationIdStringrequiredThe unique Id of the Application you are requesting to log into.
loginIdStringrequiredThe login identifier of the user. The login identifier can be one of the following (see loginIdTypes for information on which of these identifiers will be used):
- Email address
- Phone number (if
phoneNumberis included in loginIdTypes ) - Username
For email and username , the value will be used exactly as provided to resolve a user. If the provided value contains leading or trailing white space, these characters will not be removed, and then would only match if the values stored in FusionAuth also contain these same leading or trailing spaces.
For phoneNumber , loginId can be any valid phone number (in E.164, national, or international format) and FusionAuth will canonicalize the value. The User will be resolved if the user’s E.164 formatted phone number matches the canonical E.164 phone number from loginId . If no country code is provided, a US/NANP country code of 1 is assumed.
loginId used here. If you supplied a username or email address loginId, the message will be sent via email. If you supplied a phone number loginId then the message will be delivered via an SMS messenger.loginIdTypesArray<String>Defaults to [email, username]Available since 1.59.0The identity types that FusionAuth will compare the loginId to. Can be one or more of the following:
emailphoneNumberusername
["email", "username"] is supplied with a loginId value of terry@example.com, then a user with terry@example.com as their email address will match first before any user with terry@example.com as their username.stateObjectAn optional object that will be returned un-modified when you complete the passwordless login request. This may be useful to return the user to particular state once they complete login using the passwordless code.
loginStrategyStringAvailable since 1.59.0The process by which the user will complete the passwordless login. The possible values are:
ClickableLink- send the user a code with a clickable link.FormField- send the user a short code intended to be manually entered into a form field.
If not specified, the default is based on the loginIdType of loginId:
- email address or username -
ClickableLink - phone number -
FormField
Example Request JSON
{
"applicationId": "10000000-0000-0002-0000-000000000001",
"loginId": "jared@piedpiper.com",
"loginIdTypes": [
"email"
],
"state": {
"client_id": "10000000-0000-0002-0000-000000000001",
"redirect_uri": "https://piedpiper.com/callback",
"response_type": "code",
"scope": "openid",
"state": "CSRF123"
}
} Response
Response Codes
| Code | Description |
|---|---|
| 200 | The request was successful. |
| 400 | The request was invalid and/or malformed. The response will contain an Errors JSON Object with the specific errors. |
| 401 | You did not supply a valid Authorization header. The header was omitted or your API key was not valid. The response will be empty. See Authentication. |
| 404 | The user was not found. The response will be empty. |
| 500 | There was an internal error. A stack trace is provided and logged in the FusionAuth log files. The response will be empty. |
Response Body
codeStringThe unique code used to complete the login request.
Example Response JSON
{
"code": "CynAUMCHLxCCAWyHXOVWPQd8ZY0a6U0e3YpYkT0MNxs"
} Send Passwordless Login
This API allows you to send an email or SMS message to a user that will contain a code that can be used to complete login. This API should be used if you want to build your own login page.
If you plan to utilize the FusionAuth login page then you will not need to use this API. Instead, once passwordless authentication is enabled for the FusionAuth Application, a new button will be presented to the user on the login page which will allow them to request an email or SMS message.
This API does not require authentication.
Request
Available Since Version 1.11.0.
Request Headers
X-FusionAuth-TenantIdStringThe unique Id of the tenant used to scope this API request.
The tenant Id is not required on this request even when more than one tenant has been configured because the tenant can be identified based upon the request parameters or it is otherwise not required.
Specify a tenant Id on this request when you want to ensure the request is scoped to a specific tenant. The tenant Id may be provided through this header or by using a tenant locked API key to achieve the same result.
See Making an API request using a Tenant Id for additional information.
Request Body
codeStringrequiredAvailable since 1.11.0The unique code to send via email or SMS, used to complete the login request. This value can be generated with a call to the Start Passwordless Login API. The loginStrategy value used in the Start Passwordless Login API controls whether an email or SMS is sent.
Example Request JSON
{
"code": "CynAUMCHLxCCAWyHXOVWPQd8ZY0a6U0e3YpYkT0MNxs"
} - This usage of the API may be removed at a later date. Once available prefer the usage outlined above which is available beginning in
1.11.0which means you will need to use the Start API prior to calling this API. - Passwordless login with phone numbers, introduced in version
1.59.0, is not supported by this usage of this API endpoint. Use the Start Passwordless Login API to obtain a code and then provide that code to this API (see above).
Request Headers
X-FusionAuth-TenantIdStringThe unique Id of the tenant used to scope this API request.
The tenant Id is not required on this request even when more than one tenant has been configured because the tenant can be identified based upon the request parameters or it is otherwise not required.
Specify a tenant Id on this request when you want to ensure the request is scoped to a specific tenant. The tenant Id may be provided through this header or by using a tenant locked API key to achieve the same result.
See Making an API request using a Tenant Id for additional information.
Request Body
applicationIdStringrequiredThe unique Id of the Application you are requesting to log into.
loginIdStringrequiredThe login identifier of the user. The login identifier can be either the email or the username .
stateObjectAn optional object that will be returned un-modified when you complete the passwordless login request. This may be useful to return the user to particular state once they complete login using the email link.
Example Request JSON
{
"applicationId": "10000000-0000-0002-0000-000000000001",
"loginId": "jared@piedpiper.com",
"state": {
"client_id": "10000000-0000-0002-0000-000000000001",
"redirect_uri": "https://piedpiper.com/callback",
"response_type": "code",
"scope": "openid",
"state": "CSRF123"
}
} Response
The response for this API does not contain a body. It only contains a status code.
Response Codes
| Code | Description |
|---|---|
| 200 | The request was successful. |
| 400 | The request was invalid and/or malformed. The response will contain an Errors JSON Object with the specific errors. |
| 500 | There was an internal error. A stack trace is provided and logged in the FusionAuth log files. The response will be empty. |
Complete a Passwordless Login
This API is used to complete the passwordless login request. This API should be used if you want to build your own login page.
If you plan to utilize the FusionAuth login page then you will not need to use this API. Instead, once passwordless authentication is enabled for the FusionAuth Application, a new button will be presented to the user on the login page which will allow them to request an email.
This API does not require authentication.
Request
Request Headers
X-Forwarded-ForStringThe IP address of a client requesting authentication. If the IP address is provided it will be stored for login history of the user. It is generally preferred to specify the IP address in the request body. If it is not provided in the request body this header value will be used if available, the request body value will take precedence.
X-FusionAuth-TenantIdStringThe unique Id of the tenant used to scope this API request.
The tenant Id is not required on this request even when more than one tenant has been configured because the tenant can be identified based upon the request parameters or it is otherwise not required.
Specify a tenant Id on this request when you want to ensure the request is scoped to a specific tenant. The tenant Id may be provided through this header or by using a tenant locked API key to achieve the same result.
See Making an API request using a Tenant Id for additional information.
Request Cookies
fusionauth.trustStringThe Two Factor Trust identifier returned by the Two Factor Login API response. This value may be provided to bypass the Two Factor challenge when a User has Two Factor enabled. When this cookie exists on the request it will take precedence over the twoFactorTrustId if provided in the request body.
Request Parameters
applicationIdStringThe unique Id of the Application you are requesting to log into. If omitted, no application-specific settings such as lambdas or templates will be applied.
codeStringrequiredThe unique code sent via email used to complete the login request.
ipAddressStringThe IP address of the end-user that is logging into FusionAuth. If this value is omitted FusionAuth will attempt to obtain the IP address of
the client, the value will be that of the X-Forwarded-For header if provided or the last proxy that sent the request. The IP address will
be stored in the User login history.
metaData.device.descriptionStringA human readable description of the device used during login. This meta data is used to describe the refresh token that may be generated for this login request.
metaData.device.nameStringA human readable name of the device used during login. This meta data is used to describe the refresh token that may be generated for this login request.
metaData.device.typeStringThe type of device represented by the device parameter. This meta data is used to describe the refresh token that may be generated for this login request.
Prior to version 1.46.0, this value was restricted to the following types:
BROWSERDESKTOPLAPTOPMOBILEOTHERSERVERTABLETTVUNKNOWN
In version 1.46.0 and beyond, this value can be any string value you’d like, have fun with it!
noJWTBooleanDefaults to falseWhen this value is set to true a JWT will not be issued as part of this request. The response body will not contain the token or refreshToken fields, and the access_token and refresh_token cookies will not be written to the HTTP response.
This optional parameter may be helpful when performing high volume authentication requests and the JWT is not being utilized, in this scenario removing the additional latency required to issue and sign the JWT may have a measurable cumulative effect on performance.
twoFactorTrustIdStringThe Two Factor Trust identifier returned by the Two Factor Login API response. This value may be provided to bypass the Two Factor challenge when a User has Two Factor enabled.
Example Request JSON
{
"applicationId": "10000000-0000-0002-0000-000000000001",
"code": "CynAUMCHLxCCAWyHXOVWPQd8ZY0a6U0e3YpYkT0MNxs"
} Response
Response Codes
| Code | Description |
|---|---|
| 200 | The authentication was successful. The response will contain the User object that was authenticated. |
| 202 | The user was authenticated successfully. The user is not registered for the application specified by the applicationId on the request. The response will contain the User object that was authenticated. |
| 203 | The user was authenticated successfully. The user is required to change their password, the response will contain the changePasswordId to be used on the Change Password API. Since version 1.15.0, the response will also contain a changePasswordReason field which can have one of the following values:
Example Response JSON |
| 212 | The user was authenticated successfully. The user’s email address (if an email address or username was used to authenticate) or phone number has not yet been verified. The response will contain the User object that was authenticated. If the tenant verification strategy has been set to FormField, the response will contain the verification Id that was generated for the user. |
| 213 | The user was authenticated successfully. The user’s registration has not yet been verified. The response will contain the User object that was authenticated. If the application’s emailConfiguration.verificationStrategy has been set to FormField, the response will contain the registrationVerificationId that was generated for the user. Prior to version 1.27.0, this status code was not returned, and you will see a 200 instead. |
| 242 | The user was authenticated successfully. The user has two factor authentication enabled. Since version 1.42.0, this status code is also returned when two factor authentication is required. The response will contain the twoFactorId to be used on the Complete Two Factor Authentication API.Example Response JSON |
| 400 | The request was invalid and/or malformed. The response will contain an Errors JSON Object with the specific errors. |
| 404 | The user was not found or the password was incorrect. The response will be empty. |
| 409 | The user is currently in an action that has prevented login. The response will contain the actions that prevented login. Example Response JSON |
| 410 | The user has expired. The response will be empty. |
| 423 | The user is locked and cannot login. The response will be empty. Prior to version 1.9.0 a 404 status code will be returned instead. |
| 500 | There was an internal error. A stack trace is provided and logged in the FusionAuth log files. The response will be empty. |
| 503 | The search index is not available or encountered an exception so the request cannot be completed. The response will contain a JSON body. |
| 504 | One or more Webhook endpoints returned an invalid response or were unreachable. Based on the transaction configuration for this event your action cannot be completed. A stack trace is provided and logged in the FusionAuth log files. |
Response Body
emailVerificationIdStringAn email verification Id, which is needed when performing your own email verification using the /api/user/verify-email API.
This field is only returned when the tenant.emailConfiguration.verificationStrategy is set to FormField.
identityVerificationIdStringAvailable since 1.59.0An identity verification Id, which is needed when performing your own identity verification using the /api/identity/verify API.
This field is only returned under the following conditions, based on the identity that was used to log in:
- An email address - the tenant.emailConfiguration.verificationStrategy is set to
FormField. - A phone number - the tenant.phoneConfiguration.verificationStrategy is set to
FormField.
refreshTokenStringThe refresh token that can be used to obtain a new access token once the provided one has expired.
Because a refresh token is per user and per application, this value will only be returned when an applicationId was provided on the login request and the user is registered to the application.
You must explicitly allow generation of refresh tokens when using the Login API.
Configure the application.loginConfiguration.generateRefreshTokens setting via the API or enable the setting by navigating to the Application -> My Application -> Security tab.
refreshTokenIdStringAvailable since 1.37.0When the refreshToken is returned in the response, this field will also be returned. This unique Id is the persistent identifier for this refresh token, and will not change even when using one-time use refresh tokens. This value may optionally be used to revoke the token using the Refresh Token API.
stateObjectIf authenticated using a One Time Password and state was provided during the Change Password request this value will be returned exactly as it was provided.
stateObjectIf state was provided during the passwordless login send request this value will be returned exactly as it was provided.
tokenStringAvailable since 1.16.0The access token, this string is an encoded JSON Web Token (JWT).
When the user will be sent a setup password email or sms message, this token will not be returned.
tokenExpirationInstantLongAvailable since 1.33.0The instant the token will expire. If the response does not contain a token , this field will also be omitted from the response.
user.activeBooleanTrue if the User is active. False if the User has been deactivated. Deactivated Users will not be able to log in.
user.birthDateStringThe User’s birthdate formatted as YYYY-MM-DD
user.breachedPasswordLastCheckedInstantLongThe instant this user’s password was last checked to determine if it is compromised.
user.connectorIdUUIDAvailable since 1.18.0The unique Id of the Connector associated with the System of Record being used to authenticate the user.
user.cleanSpeakIdUUIDThis Id is used by FusionAuth when the User’s username is sent to CleanSpeak to be moderated (filtered and potentially sent to the approval queue). It is the content Id of the username inside CleanSpeak.
user.dataObjectAn object that can hold any information about the User that should be persisted.
user.data.emailStringThis field will be used as the email address if no user.email field is found.
This feature was removed in version 1.26.0 and added back in 1.27.2.
user.emailStringThe User’s email address.
user.expiryLongThe expiration instant of the User’s account. An expired user is not permitted to log in.
user.firstNameStringThe first name of the User.
user.fullNameStringThe User’s full name as a separate field that is not calculated from firstName and lastName .
user.idUUIDThe User’s unique Id.
user.identitiesArrayAvailable since 1.59.0The list of identities that exist for a User.
user.identities[x].displayValueStringAvailable since 1.59.0The display value for the identity. Only used for username type identities. If the unique username feature is not enabled, this value
will be the same as user.identities[x].value . Otherwise, it will be the username the User has chosen. For
primary username identities, this will be the same value as user.username .
user.identities[x].insertInstantLongAvailable since 1.59.0The instant when the identity was created.
user.identities[x].lastLoginInstantLongAvailable since 1.59.0The instant when the identity was last used to log in. If a User has multiple identity types (username, email, and phoneNumber), then this value will represent the specific identity they last used to log in. This contrasts with user.lastLoginInstant , which represents the last time any of the User’s identities was used to log in.
Identity provider logins will not be reflected here (see user.lastLoginInstant for a field that includes identity provider logins).
user.identities[x].lastUpdateInstantLongAvailable since 1.59.0The instant when the identity was last updated.
user.identities[x].moderationStatusStringAvailable since 1.59.0The current status of the username. This is used if you are moderating usernames via CleanSpeak. The possible values are:
ACTIVE- the username is activePENDING- the username is pending approval/moderationREJECTED- the username was rejected during moderation
If a username has been rejected, it is still possible to allow the User to update it and have the new one moderated again.
Only used for username type identities. For primary username identities, this will be the same value as user.usernameStatus .
user.identities[x].typeStringAvailable since 1.59.0The identity type. The possible values are:
email- identities defined by an email addressphoneNumber- identities defined by a phone numberusername- identities defined by a username
user.identities[x].valueStringAvailable since 1.59.0The value represented by the identity. The contents of this field depend on user.identities[x].type and will be one of the following:
- Email address - The User’s email address, always lower cased. For primary email identities, this will be the same value as user.email
- Phone number - The User’s phone number, in E.164 canonical format. For primary phone number identities, this will be the same value as user.phoneNumber
- Username - User’s username - this will be the same as user.identities[x].displayValue . For primary username identities, this will be the same value as user.username
This value is unique within a tenant for a particular user.identities[x].type .
If the unique usernames feature is enabled, value will be the unique username (within the tenant). For primary username identities, this will also be the same value as user.uniqueUsername .
user.identities[x].verifiedBooleanAvailable since 1.59.0Whether verification was actually performed on the identity by FusionAuth. This is used in combination with the user.identities[x].verifiedReason to decide whether an identity needs verification.
user.identities[x].verifiedInstantLongAvailable since 1.59.0The instant when verification was performed on the identity. This field is only populated when verification was actually performed on the identity by FusionAuth.
user.identities[x].verifiedReasonStringAvailable since 1.59.0The reason the User’s identity was verified or not verified. The possible values are:
Skipped- Verification was skipped due to theskipVerificationparameter on the requestTrusted- Identity was created via an identity provider or a connectorUnverifiable- FusionAuth doesn’t know how to verify this identity type. Usernames are an exampleImplicit- Verification was implicitly performed by sending a set password or passwordless messagePending- Tenant policy requires verification but no verification has been performed yetCompleted- Verification was performed by FusionAuthDisabled- Tenant policy did not require verificationImport- User was imported so verification was not performed by FusionAuth
If this field is Disabled, Import, Skipped, Trusted, or Unverifiable, then verification will not be required, regardless of the user.identities[x].verified value.
For Implicit, Pending, or Completed, the identity will require verification if user.identities[x].verified is false.
user.imageUrlStringThe URL that points to an image file that is the User’s profile image.
user.insertInstantLongThe instant when the user was created.
user.lastLoginInstantLongThe instant when the User logged in last. See user.identities[x].lastLoginInstant for more granular information based on identity.
user.lastNameStringThe User’s last name.
user.lastUpdateInstantLongThe instant when the User was last updated.
user.membershipsArrayThe list of memberships for the User.
user.memberships[x].dataObjectAn object that can hold any information about the User for this membership that should be persisted.
user.memberships[x].groupIdUUIDThe Id of the Group of this membership.
user.memberships[x].idUUIDThe unique Id of this membership.
user.memberships[x].insertInstantLongThe instant that the membership was created.
user.middleNameStringThe User’s middle name.
user.mobilePhoneStringThe User’s mobile phone number. This is useful if you will be sending push notifications or SMS messages to the User.
This differs from user.phoneNumber and cannot be used to log in.
user.parentEmailStringAvailable since 1.7.0The email address of the user’s parent or guardian. If this value was provided during a create or update operation, this value will only remain until the child is claimed by a parent.
user.passwordChangeRequiredBooleanIndicates that the User’s password needs to be changed during their next login attempt.
user.passwordLastUpdateInstantLongThe instant that the User last changed their password.
user.phoneNumberStringAvailable since 1.59.0The User’s primary phone number. The phone number is stored and returned in E.164 canonical format, however a phone number is considered unique regardless of the format. 303-555-1212 is considered equal to +13035551212 so either version of this phone number can be used whenever providing it as input to an API.
This differs from user.mobilePhone in that user.phoneNumber can be used to log in, just like an email address or a username.
user.preferredLanguagesArray<String>An array of locale strings that give, in order, the User’s preferred languages. These are important for email templates and other localizable text. See Locales.
user.registrationsArrayThe list of registrations for the User. This will include registrations for inactive applications.
user.registrations[x].applicationIdUUIDThe Id of the Application that this registration is for.
user.registrations[x].authenticationTokenStringThe Authentication Token for this registration (if one exists).
user.registrations[x].cleanSpeakIdUUIDThis Id is used by FusionAuth when the User’s username for this registration is sent to CleanSpeak to be moderated (filtered and potentially sent to the approval queue). It is the content Id of the username inside CleanSpeak.
user.registrations[x].dataObjectAn object that can hold any information about the User for this registration that should be persisted.
user.registrations[x].idUUIDThe Id of this registration.
user.registrations[x].insertInstantLongThe instant that this registration was created.
user.registrations[x].lastLoginInstantLongThe instant that the User last logged into the Application for this registration.
user.registrations[x].preferredLanguagesArray<String>An array of locale strings that give, in order, the User’s preferred languages for this registration. These are important for email templates and other localizable text.
user.registrations[x].rolesArray<String>The list of roles that the User has for this registration. The string is the role’s Name not the role’s Id, e.g. admin or user-role.
user.registrations[x].timezoneStringThe User’s preferred timezone for this registration. The string will be in an IANA time zone format.
user.registrations[x].tokensMap<String,StringDEPRECATEDA map that contains tokens returned from identity providers.
For example, if this user has authenticated using the Facebook Identity Provider, the Facebook access token will be available in this map, keyed by name Facebook. For an OpenID Connect Identity provider, or other generic providers, if a token is stored it will be keyed by the Identity Provider unique Id.
The token returned and stored from the Identity Provider is now stored in the IdP link and is retrievable using the Identity Provider Link API.
user.registrations[x].usernameStringThe username of the User for this registration only. This is for display purposes and cannot be used to log in.
user.registrations[x].usernameStatusStringThe current status of the username. This is used if you are moderating usernames via CleanSpeak. The possible values are:
ACTIVE- the username is activePENDING- the username is pending approval/moderationREJECTED- the username was rejected during moderation
If a username has been rejected, it is still possible to allow the User to update it and have the new one moderated again.
user.registrations[x].verifiedBooleanThis value indicates if this User’s registration has been verified.
For additional information, see these tutorials:
user.registrations[x].verifiedInstantLongAvailable since 1.48.0The instant that this registration was verified.
user.tenantIdUUIDThe Id of the Tenant that this User belongs to.
user.timezoneStringThe User’s preferred timezone. This can be used as a default to display instants, and it is recommended that you allow Users to change this per-session. The string will be in an IANA time zone format.
user.twoFactor.methods[x].authenticator.algorithmStringThe algorithm used by the TOTP authenticator. With the current implementation, this will always be HmacSHA1.
user.twoFactor.methods[x].authenticator.codeLengthIntegerThe length of code generated by the TOTP. With the current implementation, this will always be 6.
user.twoFactor.methods[x].authenticator.timeStepIntegerThe time-step size in seconds. With the current implementation, this will always be 30.
user.twoFactor.methods[x].emailStringThe value of the email address for this method. Only present if user.twoFactor.methods[x].method is email.
user.twoFactor.methods[x].idStringThe unique Id of the method.
user.twoFactor.methods[x].lastUsedBooleantrue if this method was used most recently.
user.twoFactor.methods[x].methodStringThe type of this method. There will also be an object with the same value containing additional information about this method. The possible values are:
authenticatoremailsms
user.twoFactor.methods[x].mobilePhoneStringThe value of the mobile phone for this method. Only present if user.twoFactor.methods[x].method is sms.
user.twoFactorDeliveryStringDEPRECATEDThe User’s preferred delivery for verification codes during a two factor login request.
The possible values are:
NoneTextMessage
user.twoFactorEnabledBooleanDEPRECATEDDetermines if the User has two factor authentication enabled for their account or not.
Removed in 1.26.0user.usernameStringThe username of the User.
user.usernameStatusStringThe current status of the username. This is used if you are moderating usernames via CleanSpeak. The possible values are:
ACTIVE- the username is activePENDING- the username is pending approval/moderationREJECTED- the username was rejected during moderation
If a username has been rejected, it is still possible to allow the User to update it and have the new one moderated again.
user.verifiedBooleanDEPRECATEDWhether or not the User’s primary email identity has been verified. This does NOT indicate whether phone number identity types are verified.
For additional information, see these tutorials:
Deprecated since 1.59.0See user.identities[x].verified and user.identities[x].verifiedReason .
user.verifiedInstantLongAvailable since 1.48.0The first instant that the User’s primary email address or phone number was verified. This value is immutable and cannot change for a user once set.
Example Response JSON
{
"token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE0ODUxNDA5ODQsImlhdCI6MTQ4NTEzNzM4NCwiaXNzIjoiYWNtZS5jb20iLCJzdWIiOiIyOWFjMGMxOC0wYjRhLTQyY2YtODJmYy0wM2Q1NzAzMThhMWQiLCJhcHBsaWNhdGlvbklkIjoiNzkxMDM3MzQtOTdhYi00ZDFhLWFmMzctZTAwNmQwNWQyOTUyIiwicm9sZXMiOltdfQ.Mp0Pcwsz5VECK11Kf2ZZNF_SMKu5CgBeLN9ZOP04kZo",
"state": {
"client_id": "10000000-0000-0002-0000-000000000001",
"redirect_uri": "https://piedpiper.com/callback",
"response_type": "code",
"scope": "openid",
"state": "CSRF123"
},
"user": {
"active": true,
"birthDate": "1976-05-30",
"connectorId": "e3306678-a53a-4964-9040-1c96f36dda72",
"data": {
"displayName": "Johnny Boy",
"favoriteColors": [
"Red",
"Blue"
]
},
"email": "example@fusionauth.io",
"expiry": 1571786483322,
"firstName": "John",
"fullName": "John Doe",
"id": "00000000-0000-0001-0000-000000000000",
"identities": [
{
"insertInstant": 1742936980069,
"lastLoginInstant": 1742936980069,
"lastUpdateInstant": 1742936980069,
"primary": true,
"type": "email",
"value": "example@fusionauth.io",
"verified": false,
"verifiedReason": "Disabled"
},
{
"insertInstant": 1742936980069,
"lastLoginInstant": 1742936980069,
"lastUpdateInstant": 1742936980069,
"primary": true,
"type": "phoneNumber",
"value": "+13035551212",
"verified": false,
"verifiedReason": "Disabled"
},
{
"displayValue": "johnny123",
"insertInstant": 1742936980069,
"lastLoginInstant": 1742936980069,
"lastUpdateInstant": 1742936980069,
"moderationStatus": "ACTIVE",
"primary": true,
"type": "username",
"value": "johnny123",
"verified": false,
"verifiedReason": "Unverifiable"
}
],
"imageUrl": "http://65.media.tumblr.com/tumblr_l7dbl0MHbU1qz50x3o1_500.png",
"insertInstant": 1742936980069,
"lastLoginInstant": 1742936980069,
"lastName": "Doe",
"middleName": "William",
"mobilePhone": "303-555-1234",
"passwordChangeRequired": false,
"passwordLastUpdateInstant": 1742936980069,
"phoneNumber": "+13035551212",
"preferredLanguages": [
"en",
"fr"
],
"registrations": [
{
"applicationId": "10000000-0000-0002-0000-000000000001",
"data": {
"displayName": "Johnny",
"favoriteSports": [
"Football",
"Basketball"
]
},
"id": "00000000-0000-0002-0000-000000000000",
"insertInstant": 1742936980069,
"lastLoginInstant": 1742936980069,
"preferredLanguages": [
"en",
"fr"
],
"roles": [
"user",
"community_helper"
],
"username": "johnny123",
"usernameStatus": "ACTIVE",
"verified": true,
"verifiedInstant": 1742936980069
}
],
"timezone": "America/Denver",
"tenantId": "f24aca2b-ce4a-4dad-951a-c9d690e71415",
"twoFactor": {
"methods": [
{
"authenticator": {
"algorithm": "HmacSHA1",
"codeLength": 6,
"timeStep": 30
},
"id": "35VW",
"method": "authenticator"
},
{
"id": "V7SH",
"method": "sms",
"mobilePhone": "555-555-5555"
},
{
"email": "example@fusionauth.io",
"id": "7K2G",
"method": "email"
}
]
},
"usernameStatus": "ACTIVE",
"username": "johnny123",
"verified": true,
"verifiedInstant": 1742936980069
}
} Response Cookies
access_tokenStringThe encoded access token. This cookie is written in the response as an HTTP Only session cookie.
refresh_tokenStringThe refresh token. This cookie is written in the response as an HTTP only persistent cookie. The cookie expiration is configured in the JWT configuration for the application or the global JWT configuration.