Update a User’s attributes.
/send endpoint and include that User’s user_id. This adds the new factor in an unverified state. If the User completes authentication within 5 minutes of the /send request, the factor becomes verified and remains on the User. If not, the factor is removed, and future login attempts with that phone number create a new User.This flow helps prevent account takeover.Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
The unique ID of a specific User. You may use an external_id here if one is set for the user.
Request type
The name of the user. Each field in the name object is optional.
Provided attributes to help with fraud detection. These values are pulled and passed into Stytch endpoints by your application.
An identifier that can be used in API calls wherever a user_id is expected. This is a string consisting of alphanumeric, ., _, -, or | characters with a maximum length of 128 characters.
Roles to explicitly assign to this User. See the RBAC guide for more information about role assignment.
Successful response
Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we may ask for this value to help identify a specific API call when helping you debug an issue.
The unique ID of the updated User.
An array of email objects for the User.
An array of phone number objects linked to the User.
An array contains a list of all crypto wallets for a given User in the Stytch API.
The user object affected by this API call. See the Get user endpoint for complete response field details.
The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors.