Get transaction account in PocketSmith
A documented PocketSmith 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
Get transaction account
- GETReads data · Transaction Accounts
api.pocketsmith.com/transaction_accounts/{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 PocketSmith 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 PocketSmith operations
- Create an account in userPOST · changes data
- Update the display order of accounts in userPUT · changes data
- Create event in scenarioPOST · changes data
- Create category in userPOST · changes data
- Create attachment in userPOST · changes data
- Create institution in userPOST · changes data
- Delete eventDELETE · changes data
- Update eventPUT · changes data
Questions
- Can HumDay get transaction account in PocketSmith?
- Yes. This operation is published in PocketSmith'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 PocketSmith account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in PocketSmith.
- 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 PocketSmith account.
Where this came from
Read from a published API description for PocketSmith at raw.githubusercontent.com/pocketsmith/api/master/openapi.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.