Boolean

link GraphQL Schema definition

link Require by

• ArchiveAccountArchive account and revoke refresh tokens. User must be verified and confirm password.
• DeleteAccountDelete account permanently or make `user.is_active=False`. The behavior is defined on settings. Anyway user refresh tokens are revoked. User must be verified and confirm password.
• DjangoDebugSQLRepresents a single database query made to a Django managed DB.
• Mutationnull
• ObtainJSONWebTokenObtain JSON web token for given user. Allow to perform login with different fields, and secondary email if set. The fields are defined on settings. Not verified users can login by default. This can be changes on settings. If user is archived, make it unarchive and return `unarchiving=True` on output.
• PageInfoThe Relay compliant `PageInfo` type, containing data necessary to paginate this connection.
• PasswordChangeChange account password when user knows the old password. A new token and refresh token are sent. User must be verified.
• PasswordResetChange user password without old password. Receive the token that was sent by email. If token and new passwords are valid, update user password and in case of using refresh tokens, revoke all of them. Also, if user has not been verified yet, verify it.
• PasswordSetSet user password - for passwordless registration Receive the token that was sent by email. If token and new passwords are valid, set user password and in case of using refresh tokens, revoke all of them. Also, if user has not been verified yet, verify it.
• Querynull
• QuizQuestionChoiceTypenull
• RefreshTokenSame as `grapgql_jwt` implementation, with standard output.
• RegisterRegister user with fields defined in the settings. If the email field of the user model is part of the registration fields (default), check if there is no user with that email or as a secondary email. If it exists, it does not register the user, even if the email field is not defined as unique (default of the default django user model). When creating the user, it also creates a `UserStatus` related to that user, making it possible to track if the user is archived, verified and has a secondary email. Send account verification email. If allowed to not verified users login, return token.
• RegisterUserOrgInfonull
• RemoveSecondaryEmailRemove user secondary email. Require password confirmation.
• ResendActivationEmailSends activation email. It is called resend because theoretically the first activation email was sent when the user registered. If there is no user with the requested email, a successful response is returned.
• RevokeTokenSame as `grapgql_jwt` implementation, with standard output.
• SendPasswordResetEmailSend password reset email. For non verified users, send an activation email instead. Accepts both primary and secondary email. If there is no user with the requested email, a successful response is returned.
• SendSecondaryEmailActivationSend activation to secondary email. User must be verified and confirm password.
• SessionTypenull
• SwapEmailsSwap between primary and secondary emails. Require password confirmation.
• TraineeTypenull
• UpdateAccountUpdate user model fields, defined on settings. User must be verified.
• UpdateUserMutationnull
• UserNodenull
• UserTypenull
• VerifyAccountVerify user account. Receive the token that was sent by email. If the token is valid, make the user verified by making the `user.status.verified` field true.
• VerifySecondaryEmailVerify user secondary email. Receive the token that was sent by email. User is already verified when using this mutation. If the token is valid, add the secondary email to `user.status.secondary_email` field. Note that until the secondary email is verified, it has not been saved anywhere beyond the token, so it can still be used to create a new account. After being verified, it will no longer be available.
• VerifyTokenSame as `grapgql_jwt` implementation, with standard output.
• __DirectiveA Directive provides a way to describe alternate runtime execution and type validation behavior in a GraphQL document. In some cases, you need to provide options to alter GraphQL's execution behavior in ways field arguments will not suffice, such as conditionally including or skipping a field. Directives provide this by describing additional information to the executor.
• __EnumValueOne possible value for a given Enum. Enum values are unique values, not a placeholder for a string or numeric value. However an Enum value is returned in a JSON response as a string.
• __FieldObject and Interface types are described by a list of Fields, each of which has a name, potentially a list of arguments, and a return type.
• __TypeThe fundamental unit of any GraphQL Schema is the type. There are many kinds of types in GraphQL as represented by the `__TypeKind` enum. Depending on the kind of a type, certain fields describe information about that type. Scalar types provide no information beyond a name and description, while Enum types provide their values. Object and Interface types provide the fields they describe. Abstract types, Union and Interface, provide the Object types possible at runtime. List and NonNull types compose other types.