Performance Improvements

Account Refreshes on Behalf of the User

Yodlee refreshes all user accounts once daily; you do not need to make any API calls to refresh the account. Any form of continuous account refreshes on behalf of the user should not be used. For example, the account refreshes every 4 hours.

For any bulk processing needs, you can call our DataExtract requests to extract for all your users in an asynchronous and incremental fashion. If you have a business case that cannot be fulfilled by any of these capabilities, please reach out to our customer success manager or client partner.

Reduce Latency in Case of Large Data

While working with large data, network latency can be an issue. We highly recommend sending the 'Accept-Encoding: gzip' header in your requests. This will enable the response to be gzipped (compressed), reducing the latency you may be experiencing.

Also, the number of transactions returned depends on multiple factors such as the selected date range, user habits, location, etc. The performance of the Transaction API is directly related to the number of transactions that are being processed. Hence with YSL 1.1, we have enabled pagination by default in the Transactions API, so only 500 transactions are returned per page, along with information to retrieve additional pages. If you use legacy REST or SOAP requests, be diligent about the date range you send for the transactions API, historical balances, and transaction summary. You should consider the worst case and implement it accordingly to deliver the right user experience.

Implement Cache for Provider API

The Get All Provider API takes more than one second to execute due to the amount of data that it provides. It is recommended to implement your cache to avoid making multiple calls to the server because this data rarely changes.