The Member Object represents an individual end user’s account belonging to a specific Organization, uniquely identified within that Organization by their email address.
Globally unique UUID that identifies a specific Organization. The organization_id is critical to perform operations on an Organization, so be sure to preserve this value. You may also use the organization_slug or organization_external_id here as a convenience.
Globally unique UUID that identifies a specific Member. The member_id is critical to perform operations on a Member, so be sure to preserve this value. You may use an external_id here if one is set for the member.
The email address of the Member.
The status of the Member. The possible values are: pending, invited, active, or deleted.
The name of the Member.
An array of registered SAML Connection or OIDC Connection objects the Member has authenticated with.
Identifies the Member as a break glass user - someone who has permissions to authenticate into an Organization by bypassing the Organization's settings. A break glass account is typically used for emergency purposes to gain access outside of normal authentication procedures. Refer to the Organization object and its auth_methods and allowed_auth_methods fields for more details.
Globally unique UUID that identifies a Member's password.
A list of OAuth registrations for this member.
Whether or not the Member's email address is verified.
Whether or not the Member's phone number is verified.
Whether or not the Member has the stytch_admin Role. This Role is automatically granted to Members
who create an Organization through the discovery flow. See the
RBAC guide for more details on this Role.
Globally unique UUID that identifies a TOTP instance.
A list of retired email addresses for this member. A previously active email address can be marked as retired in one of two ways:
A retired email address cannot be used by other Members in the same Organization. However, unlinking retired email addresses allows them to be subsequently re-used by other Organization Members. Retired email addresses can be unlinked using the Unlink Retired Email endpoint.
Whether the Member is temporarily locked due to too many failed authentication attempts. See the User Locking Guide for more information.
Sets whether the Member is enrolled in MFA. If true, the Member must complete an MFA step whenever they wish to log in to their Organization. If false, the Member only needs to complete an MFA step if the Organization's MFA policy is set to REQUIRED_FOR_ALL.
The Member's phone number. A Member may only have one phone number. The phone number should be in E.164 format (i.e. +1XXXXXXXXXX).
The Member's default MFA method. This value is used to determine which secondary MFA method to use in the case of multiple methods registered for a Member. The current possible values are sms_otp and totp.
Explicit or implicit Roles assigned to this Member, along with details about the role assignment source. See the RBAC guide for more information about role assignment.
An arbitrary JSON object for storing application-specific data or identity-provider-specific data.
An arbitrary JSON object of application-specific data. These fields can be edited directly by the frontend SDK, and should not be used to store critical information. See the Metadata resource for complete field behavior details.
The timestamp of the Member's creation. Values conform to the RFC 3339 standard and are expressed in UTC, e.g. 2021-12-29T12:33:09Z.
The timestamp of when the Member was last updated. Values conform to the RFC 3339 standard and are expressed in UTC, e.g. 2021-12-29T12:33:09Z.
A scim member registration, referencing a SCIM Connection object in use for the Member creation.
The ID of the member given by the identity provider.
When the member 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 member 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.