Update a user in ExaVault
A documented ExaVault 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
Update a user
- PATCHChanges data · Users
accountname.exavault.com/users/{id}
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 ExaVault 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 ExaVault operations
- Create new email listPOST · changes data
- Create a userPOST · changes data
- Add A New WebhookPOST · changes data
- Create a new notificationPOST · changes data
- Creates a sharePOST · changes data
- Create a new SSH KeyPOST · changes data
- Create a folderPOST · changes data
- Send referral email to a given addressPOST · changes data
Questions
- Can HumDay update a user in ExaVault?
- Yes. This operation is published in ExaVault'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 ExaVault data?
- Yes — this is a PATCH operation, so it changes something in ExaVault. 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 ExaVault account.
Where this came from
Read from a published API description for ExaVault at exavault-website.cdn.prismic.io/exavault-website/2d2d871e-394d-433e-9305-f38b6656f279_evap. The description above is the provider’s own wording, not ours. Last published 2021-07-26.