Creates a new user. E-mail authentication is always enabled, and no password is set, meaning the only way to authenticate the newly created user is through magic link.
Human-readable user display name. This is not a unique identifier.
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.
Client metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client.
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.
Server metadata. Used as a data store, only accessible from the server side. You can store secret information related to the user here.
Primary email
Whether the primary email has been verified to belong to this user
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
Sets the user’s password. Doing so revokes all current sessions.
Enables 2FA and sets a TOTP secret for the user. Set to null to disable 2FA.
Successful response
The unique identifier of the user
Whether the primary email has been verified to belong to this user
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
The time the user signed up identify=>(the number of milliseconds since epoch, January 1, 1970, UTC)
The time the user was last active identify=>(the number of milliseconds since epoch, January 1, 1970, UTC)
Primary email
Human-readable user display name. This is not a unique identifier.
ID of the team currently selected by the user
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.
Client metadata. Used as a data store, accessible from the client side. Do not store information that should not be exposed to the client.
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.
Server metadata. Used as a data store, only accessible from the server side. You can store secret information related to the user here.