Logout from the bank in Testfire AltoroJ
A documented Testfire AltoroJ operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Logout from the bank
- GETReads data · 6. Logout
/logout
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 Testfire AltoroJ operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Testfire AltoroJ operations
- Login methodPOST · changes data
- Transfer money between two accountsPOST · changes data
- Submit feedback for the bankPOST · changes data
- Add new userPOST · changes data
- Return transactions between 2 specific datesPOST · changes data
- Change user passwordPOST · changes data
- Returns a list of all the accounts owned by the userGET · reads data
- Check if any user is logged inGET · reads data
Questions
- Can HumDay logout from the bank in Testfire AltoroJ?
- Yes. This operation is published in Testfire AltoroJ's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Testfire AltoroJ account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Testfire AltoroJ.
- 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 Testfire AltoroJ account.
Where this came from
Read from a published API description for Testfire AltoroJ at demo.testfire.net/swagger/properties.json. The description above is the provider’s own wording, not ours. Last published 2021-06-21.