1. New Features and Enhancements Summary
- The following are the new services that are made available in this release:
- Update user details.
- Get transactionSummary is exposed under derived endpoint.
- The user register, user login, and cobrand login services are enhanced to accept the locale value and will display category names as per the locale.
- The system-defined category names in the get transaction categories, get transactions & get transaction summary services will be provided in the language with the following preferences:
- User login locale
- User register locale
- Cobrand login locale
- Cobrand default locale
- If the category names are renamed by the user, the changed names will be reflected in the get transaction categories, get transactions & get transaction summary services.
- The update category service has been enhanced to rename the high-level categories.
- Category Id, high-level category ID and category source are exposed in the get transactions and get transaction summary service response.
- Category name filter is deprecated in get transactions and get transactions count API. Category ID is added as a filter.
- System-defined category ID should be provided in the filter as is.
- User- defined category ID should be provided in the filter with the prefix “U”.
- Category name filter is deprecated in get transactions and get transactions count API. Category ID is added as a filter.
- High-level category ID is accepted as an input in the get transactions service.
- The update account service has been enhanced to update the status of the account to closed along with the existing support of active and inactive status.
- The get providers service has been improved:
- Not to return sites which consists of containers only that are disabled for the customers and deprecated by Yodlee.
- To provide the country-specific popular sites for the user.
- To assure more security and ensure adherence to HTTP standards, enhancements have been done to accept sensitive parameters as body parameters and query parameters are deprecated in the cobrand and user endpoint APIs.
- The services under the derived endpoint are enhanced to provide the summary values in the user’s preferred currency.
- The get & POST provider account response is enhanced:
- aggregationSource field is exposed in the response
- actionRequired field is exposed in the response
2. New API Details
API Names |
Details |
PUT /{cobrandName}/v1/user |
The update user profile service API has been introduced to update the user details |
GET /{cobrandName}/v1/derived/transactionSummary |
The get transaction summary service has been introduced to provide the summary information of transactions grouped by category |
3. Existing API Enhancement Details
Existing API Names |
Enhancement Details |
POST /{cobrandName}/v1/user/register |
a. Existing registerParam query parameter is deprecated and a new field userParam is accepted as a body parameter that replaces registerParam b.Compared to registerParam, userParam accepts locale along with the other parameters supported by registerParam. |
POST /{cobrandName}/v1/user/login |
|
POST /{cobrandName}/v1/user/credentials
|
|
POST /{cobrandName}/v1/user/samlRegister |
Query parameter - samlResponse is deprecated and has been supported as body parameter |
POST /{cobrandName}/v1/user/samlLogin |
Query parameter - samlResponse is deprecated and has been supported as body parameter |
POST /{cobrandName}/v1/cobrand/login |
|
POST /{cobrandName}/v1/cobrand/config/notifications/events/{eventName} PUT /{cobrandName}/v1/cobrand/config/notifications/events/{eventName} |
|
PUT /{cobrandName}/v1/transactions/categories |
“highLevelCategoryName” has been added as an input in the JSON input parameter. |
GET /{cobrandName}/v1/transactions |
The parameters added in the response are:
The query parameters added are:
Note: The categoryName filter is deprecated. |
GET /{cobrandName}/v1/transactions/count |
The categoryName filter is deprecated and categoryId is added as a query parameter. |
GET /{cobrandName}/v1/providers/providerAccounts GET /{cobrandName}/v1/providers/providerAccounts/{providerAccountId} POST /{cobrandName}/v1/providers/providerAccounts PUT /{cobrandName}/v1/providers/providerAccounts |
The parameters added in the response are:
|
3. Bugs Fixed:
Certain non-English characters in API responses were provided as junk characters. This issue has been fixed.