Delete Account in Appwrite
A documented Appwrite operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Delete Account
- DELETEChanges data · account
appwrite.io/account
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Appwrite operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Appwrite operations
- Create Email VerificationPOST · changes data
- Create AccountPOST · changes data
- Create Account JWTPOST · changes data
- Update Account EmailPATCH · changes data
- Create Password RecoveryPOST · changes data
- Create Account SessionPOST · changes data
- Complete Email VerificationPUT · changes data
- Create DocumentPOST · changes data
Questions
- Can HumDay delete account in Appwrite?
- Yes. This operation is published in Appwrite's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Appwrite data?
- Yes — this is a DELETE operation, so it changes something in Appwrite. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Appwrite account.
Where this came from
Read from a published API description for Appwrite at appwrite.io/specs/open-api3?platform=client. The description above is the provider’s own wording, not ours. Last published 2021-08-12.