Delete account in Journy Developer documentation
A documented Journy Developer documentation 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 · Accounts
api.journy.io/accounts
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 Journy Developer documentation 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 Journy Developer documentation operations
- Create or update userPOST · changes data
- Link web activity to userPOST · changes data
- Add users to an accountPOST · changes data
- Remove user from accountPOST · changes data
- Create or update accountPOST · changes data
- Get user segmentsGET · reads data
- Get user propertiesGET · reads data
- Validate API keyGET · reads data
Questions
- Can HumDay delete account in Journy Developer documentation?
- Yes. This operation is published in Journy Developer documentation'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 Journy Developer documentation data?
- Yes — this is a DELETE operation, so it changes something in Journy Developer documentation. 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 Journy Developer documentation account.
Where this came from
Read from a published API description for Journy Developer documentation at api.journy.io/spec.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.