The User Object represents an individual end user’s account.
The unique ID of the affected User.
An array of email objects for the User.
The status of the User. The possible values are pending and active.
An array of phone number objects linked to the User.
An array that contains a list of all Passkey or WebAuthn registrations for a given User in the Stytch API.
An array of OAuth provider objects linked to the User.
An array containing a list of all TOTP instances for a given User in the Stytch API.
An array contains a list of all crypto wallets for a given User in the Stytch API.
An array that contains a list of all biometric registrations for a given User in the Stytch API.
Whether the User is temporarily locked due to too many failed authentication attempts. See the User Locking Guide for more information.
Roles assigned to this User. See the RBAC guide for more information about role assignment.
The name of the User. Each field in the name object is optional.
The timestamp of the User's creation. Values conform to the RFC 3339 standard and are expressed in UTC, e.g. 2021-12-29T12:33:09Z.
The password object is returned for users with a password.
An identifier that can be used in most API calls where a member_id is expected. This is a string consisting of alphanumeric, ., _, -, or | characters with a maximum length of 128 characters. External IDs must be unique within the project.
When the user lock was created, if there is one. Values conform to the RFC 3339 standard and are expressed in UTC, e.g. 2021-12-29T12:33:09Z.
When the user lock expires, if there is one. Values conform to the RFC 3339 standard and are expressed in UTC, e.g. 2021-12-29T12:33:09Z.