Account class
The Account service allows you to authenticate and manage a user account.
Constructors
- Account.new(Client client)
Properties
Methods
-
create(
{required String userId, required String email, required String password, String? name}) → Future< User> - Use this endpoint to allow a new user to register a new account in your project. After the user registration completes successfully, you can use the /account/verfication route to start verifying the user email address. To allow the new user to login to their new account, you need to create a new account session.
-
createAnonymousSession(
) → Future< Session> - Use this endpoint to allow a new user to register an anonymous account in your project. This route will also create a new session for the user. To allow the new user to convert an anonymous account to a normal account, you need to update its email and password or create an OAuth2 session.
-
createEmailPasswordSession(
{required String email, required String password}) → Future< Session> - Allow the user to login into their account by providing a valid email and password combination. This route will create a new session for the user.
-
createEmailToken(
{required String userId, required String email, bool? phrase}) → Future< Token> - Sends the user an email with a secret key for creating a session. If the provided user ID has not be registered, a new user will be created. Use the returned user ID and secret and submit a request to the POST /v1/account/sessions/token endpoint to complete the login process. The secret sent to the user's email is valid for 15 minutes.
-
createJWT(
) → Future< Jwt> - Use this endpoint to create a JSON Web Token. You can use the resulting JWT to authenticate on behalf of the current user when working with the Appwrite server-side API and SDKs. The JWT secret is valid for 15 minutes from its creation and will be invalid if the user will logout in that time frame.
-
createMagicURLToken(
{required String userId, required String email, String? url, bool? phrase}) → Future< Token> - Sends the user an email with a secret key for creating a session. If the provided user ID has not been registered, a new user will be created. When the user clicks the link in the email, the user is redirected back to the URL you provided with the secret key and userId values attached to the URL query string. Use the query string parameters to submit a request to the POST /v1/account/sessions/token endpoint to complete the login process. The link sent to the user's email address is valid for 1 hour.
-
createMfaAuthenticator(
{required AuthenticatorType type}) → Future< MfaType> - Add an authenticator app to be used as an MFA factor. Verify the authenticator using the verify authenticator method.
-
createMfaChallenge(
{required AuthenticationFactor factor}) → Future< MfaChallenge> - Begin the process of MFA verification after sign-in. Finish the flow with updateMfaChallenge method.
-
createMfaRecoveryCodes(
) → Future< MfaRecoveryCodes> - Generate recovery codes as backup for MFA flow. It's recommended to generate and show then immediately after user successfully adds their authehticator. Recovery codes can be used as a MFA verification type in createMfaChallenge method.
-
createOAuth2Token(
{required OAuthProvider provider, String? success, String? failure, List< String> ? scopes}) → Future - Allow the user to login to their account using the OAuth2 provider of their choice. Each OAuth2 provider should be enabled from the Appwrite console first. Use the success and failure arguments to provide a redirect URL's back to your app when login is completed.
-
createPhoneToken(
{required String userId, required String phone}) → Future< Token> - Sends the user an SMS with a secret key for creating a session. If the provided user ID has not be registered, a new user will be created. Use the returned user ID and secret and submit a request to the POST /v1/account/sessions/token endpoint to complete the login process. The secret sent to the user's phone is valid for 15 minutes.
-
createPhoneVerification(
) → Future< Token> - Use this endpoint to send a verification SMS to the currently logged in user. This endpoint is meant for use after updating a user's phone number using the accountUpdatePhone endpoint. Learn more about how to complete the verification process. The verification code sent to the user's phone number is valid for 15 minutes.
-
createRecovery(
{required String email, required String url}) → Future< Token> - Sends the user an email with a temporary secret key for password reset. When the user clicks the confirmation link he is redirected back to your app password reset URL with the secret key and email address values attached to the URL query string. Use the query string params to submit a request to the PUT /account/recovery endpoint to complete the process. The verification link sent to the user's email address is valid for 1 hour.
-
createSession(
{required String userId, required String secret}) → Future< Session> - Use this endpoint to create a session from token. Provide the userId and secret parameters from the successful response of authentication flows initiated by token creation. For example, magic URL and phone login.
-
createVerification(
{required String url}) → Future< Token> - Use this endpoint to send a verification message to your user email address to confirm they are the valid owners of that address. Both the userId and secret arguments will be passed as query parameters to the URL you have provided to be attached to the verification email. The provided URL should redirect the user back to your app and allow you to complete the verification process by verifying both the userId and secret parameters. Learn more about how to complete the verification process. The verification link sent to the user's email address is valid for 7 days.
-
deleteIdentity(
{required String identityId}) → Future - Delete an identity by its unique ID.
-
deleteMfaAuthenticator(
{required AuthenticatorType type}) → Future - Delete an authenticator for a user by ID.
-
deleteSession(
{required String sessionId}) → Future - Logout the user. Use 'current' as the session ID to logout on this device, use a session ID to logout on another device. If you're looking to logout the user on all devices, use Delete Sessions instead.
-
deleteSessions(
) → Future - Delete all sessions from the user account and remove any sessions cookies from the end client.
-
get(
) → Future< User> - Get the currently logged in user.
-
getMfaRecoveryCodes(
) → Future< MfaRecoveryCodes> - Get recovery codes that can be used as backup for MFA flow. Before getting codes, they must be generated using createMfaRecoveryCodes method. An OTP challenge is required to read recovery codes.
-
getPrefs(
) → Future< Preferences> - Get the preferences as a key-value object for the currently logged in user.
-
getSession(
{required String sessionId}) → Future< Session> - Use this endpoint to get a logged in user's session using a Session ID. Inputting 'current' will return the current session being used.
-
listIdentities(
{List< String> ? queries}) → Future<IdentityList> - Get the list of identities for the currently logged in user.
-
listLogs(
{List< String> ? queries}) → Future<LogList> - Get the list of latest security activity logs for the currently logged in user. Each log returns user IP address, location and date and time of log.
-
listMfaFactors(
) → Future< MfaFactors> - List the factors available on the account to be used as a MFA challange.
-
listSessions(
) → Future< SessionList> - Get the list of active sessions across different devices for the currently logged in user.
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a nonexistent method or property is accessed.
inherited
-
toString(
) → String -
A string representation of this object.
inherited
-
updateEmail(
{required String email, required String password}) → Future< User> - Update currently logged in user account email address. After changing user address, the user confirmation status will get reset. A new confirmation email is not sent automatically however you can use the send confirmation email endpoint again to send the confirmation email. For security measures, user password is required to complete this request. This endpoint can also be used to convert an anonymous account to a normal one, by passing an email address and a new password.
-
updateMagicURLSession(
{required String userId, required String secret}) → Future< Session> - Use this endpoint to create a session from token. Provide the userId and secret parameters from the successful response of authentication flows initiated by token creation. For example, magic URL and phone login.
-
updateMFA(
{required bool mfa}) → Future< User> - Enable or disable MFA on an account.
-
updateMfaAuthenticator(
{required AuthenticatorType type, required String otp}) → Future< User> - Verify an authenticator app after adding it using the add authenticator method.
-
updateMfaChallenge(
{required String challengeId, required String otp}) → Future< Session> - Complete the MFA challenge by providing the one-time password. Finish the process of MFA verification by providing the one-time password. To begin the flow, use createMfaChallenge method.
-
updateMfaRecoveryCodes(
) → Future< MfaRecoveryCodes> - Regenerate recovery codes that can be used as backup for MFA flow. Before regenerating codes, they must be first generated using createMfaRecoveryCodes method. An OTP challenge is required to regenreate recovery codes.
-
updateName(
{required String name}) → Future< User> - Update currently logged in user account name.
-
updatePassword(
{required String password, String? oldPassword}) → Future< User> - Update currently logged in user password. For validation, user is required to pass in the new password, and the old password. For users created with OAuth, Team Invites and Magic URL, oldPassword is optional.
-
updatePhone(
{required String phone, required String password}) → Future< User> - Update the currently logged in user's phone number. After updating the phone number, the phone verification status will be reset. A confirmation SMS is not sent automatically, however you can use the POST /account/verification/phone endpoint to send a confirmation SMS.
-
updatePhoneSession(
{required String userId, required String secret}) → Future< Session> - Use this endpoint to create a session from token. Provide the userId and secret parameters from the successful response of authentication flows initiated by token creation. For example, magic URL and phone login.
-
updatePhoneVerification(
{required String userId, required String secret}) → Future< Token> - Use this endpoint to complete the user phone verification process. Use the userId and secret that were sent to your user's phone number to verify the user email ownership. If confirmed this route will return a 200 status code.
-
updatePrefs(
{required Map prefs}) → Future< User> - Update currently logged in user account preferences. The object you pass is stored as is, and replaces any previous value. The maximum allowed prefs size is 64kB and throws error if exceeded.
-
updateRecovery(
{required String userId, required String secret, required String password}) → Future< Token> - Use this endpoint to complete the user account password reset. Both the userId and secret arguments will be passed as query parameters to the redirect URL you have provided when sending your request to the POST /account/recovery endpoint.
-
updateSession(
{required String sessionId}) → Future< Session> - Use this endpoint to extend a session's length. Extending a session is useful when session expiry is short. If the session was created using an OAuth provider, this endpoint refreshes the access token from the provider.
-
updateStatus(
) → Future< User> - Block the currently logged in user account. Behind the scene, the user record is not deleted but permanently blocked from any access. To completely delete a user, use the Users API instead.
-
updateVerification(
{required String userId, required String secret}) → Future< Token> - Use this endpoint to complete the user email verification process. Use both the userId and secret parameters that were attached to your app URL to verify the user email ownership. If confirmed this route will return a 200 status code.
Operators
-
operator ==(
Object other) → bool -
The equality operator.
inherited