In this last post of the Yodlee-Rails series, we put all the remaining pieces together and retrieve details bank and credit card transaction data for our users.
In this post of the Yodlee-Rails series, we learn how to manage users on Yodlee. We also cover how to auto-create and destroy Yodlee users as users join and leave your app.
We continue the series by learning how to apply object-oriented principles to effectively and efficiently render login forms from hundreds of banks.
In this post, we look at interacting with banks and other services via the Yodlee API in preparation for scraping user credit card and bank statement data.
Yodlee is a service like no other: it allows apps to aggregate consumer data from across the financial spectrum. In this first post of the series, we begin creating a Yodlee Rails app using best practices.
On October 21st, Yodlee released a new REST/JSON API to replace its current SOAP/XML API. Here is a breakdown of the changes.
Yodlee is used by banks and financial institutions worldwide to aggregate consumer data. Here is how to set up a working API connection between your Rails app and the Yodlee API service.
In this tutorial, we will take an object-oriented approach to OAuth, separating logic for OAuth users from logic for non-OAuth users to create a robust and stable implementation that is clean, sturdy, and will not break down as you scale.