Get User Details in Yodlee Core
A documented Yodlee Core 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 User Details
- GETReads data · User
/user
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 Yodlee Core 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 Yodlee Core operations
- Delete Notification SubscriptionDELETE · changes data
- Subscribe For Notification EventPOST · changes data
- Update Notification SubscriptionPUT · changes data
- Update User DetailsPUT · changes data
- Add Manual AccountPOST · changes data
- Register UserPOST · changes data
- Create CategoryPOST · changes data
- Delete DocumentDELETE · changes data
Questions
- Can HumDay get user details in Yodlee Core?
- Yes. This operation is published in Yodlee Core'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 Yodlee Core account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Yodlee Core.
- 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 Yodlee Core account.
Where this came from
Read from a published API description for Yodlee Core at developer.yodlee.com/sites/default/files/api_spec/coreapisoas3.yml. The description above is the provider’s own wording, not ours. Last published 2021-06-21.