Cobrand Login in Yodlee Core
A documented Yodlee Core 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
Cobrand Login
- POSTChanges data · Cobrand
/cobrand/login
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. Because this one changes data, it cannot run until you have explicitly granted it.
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 cobrand login 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.
- Will this change my Yodlee Core data?
- Yes — this is a POST operation, so it changes something in Yodlee Core. 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 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.