Updates a user. Only the values provided will be updated.
Documentation Index
Fetch the complete documentation index at: https://stackauth-e0affa27-chore-move-mcp-to-a-sep-app.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
The ID of the user, or the special value me for the currently authenticated user
"3241a285-8329-4d69-8f3d-316e08cf140c"
Human-readable user display name. This is not a unique identifier.
"John Doe"
URL of the profile image for user. Can be a Base64 encoded image. Must be smaller than 100KB. Please compress and crop to a square before passing in.
"https://example.com/image.jpg"
Client metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client.
{ "key": "value" }Client read-only, server-writable metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client. The client can read this data, but cannot modify it. This is useful for things like subscription status.
{ "key": "value" }Server metadata. Used as a data store, only accessible from the server side. You can store secret information related to the user here.
{ "key": "value" }Primary email
"johndoe@example.com"
Whether the primary email has been verified to belong to this user
true
Whether the primary email is used for authentication. If this is set to false, the user will not be able to sign in with the primary email with password or OTP
true
Sets the user's password. Doing so revokes all current sessions.
"my-new-password"
If password is not given, sets the user's password hash to the given string in Modular Crypt Format (ex.: $2a$10$VIhIOofSMqGdGlL4wzE//e.77dAQGqNtF/1dT7bqCrVtQuInWy2qi). Doing so revokes all current sessions.
Enables 2FA and sets a TOTP secret for the user. Set to null to disable 2FA.
"dG90cC1zZWNyZXQ="
ID of the team currently selected by the user
"team-id"
Whether the user is restricted by an administrator. Can be set manually or by sign-up rules.
false
Public reason shown to the user explaining why they are restricted. Optional.
null
Private details about the restriction (e.g., which sign-up rule triggered). Only visible to server access and above.
null
Best-effort ISO country code captured at sign-up time from request geo headers.
"US"
Successful response
The unique identifier of the user
"3241a285-8329-4d69-8f3d-316e08cf140c"
Whether the primary email has been verified to belong to this user
true
Whether the primary email is used for authentication. If this is set to false, the user will not be able to sign in with the primary email with password or OTP
true
The time the user signed up (identify) => (the number of milliseconds since epoch, January 1, 1970, UTC)
1630000000000
The time the user was last active (identify) => (the number of milliseconds since epoch, January 1, 1970, UTC)
1630000000000
Whether the user is in restricted state (has signed up but not completed onboarding requirements)
false
Whether the user is restricted by an administrator. Can be set manually or by sign-up rules.
false
User risk scores used for sign-up risk evaluation.
{
"sign_up": { "bot": 0, "free_trial_abuse": 0 }
}Primary email
"johndoe@example.com"
Human-readable user display name. This is not a unique identifier.
"John Doe"
ID of the team currently selected by the user
"team-id"
URL of the profile image for user. Can be a Base64 encoded image. Must be smaller than 100KB. Please compress and crop to a square before passing in.
"https://example.com/image.jpg"
Client metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client.
{ "key": "value" }Client read-only, server-writable metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client. The client can read this data, but cannot modify it. This is useful for things like subscription status.
{ "key": "value" }Server metadata. Used as a data store, only accessible from the server side. You can store secret information related to the user here.
{ "key": "value" }The reason why the user is restricted (e.g., type: "email_not_verified", "anonymous", or "restricted_by_administrator"), null if not restricted
null
Public reason shown to the user explaining why they are restricted. Optional.
null
Private details about the restriction (e.g., which sign-up rule triggered). Only visible to server access and above.
null
Best-effort ISO country code captured at sign-up time from request geo headers.
"US"