General FAQ

You can aggregate any of the following types of user data: bank, credit card, investments, loans, insurance, bills (such as utility, phone, etc.) and real estate. Each type of data is known as a container, which can have one or more account types; for example, a bank container can include a checking account and a savings account. For a given account, Envestnet | Yodlee can provide multiple datasets that capture various financial data attributes such as account holder name, account balance, (masked) account number, routing number, investment holdings and options, personally identifiable information (e.g., address), transactions, monthly statements, and so on. Whether a particular data element is returned is subject to its availability at the financial institution – not all institutions make all data available. Learn more about our data model here.

Personal financial data can solve problems, simplify workflows and build many applications. Some examples include apps for expense categorization, budgeting, cash flow prediction, verifying account ownership and identity in order to facilitate fund and asset transfers, managing healthcare spending, enabling credit/lending, fraud prevention, and even verifying voter identity. Learn more about the various ways our customers have innovated with personal financial data through our use cases.

Envestnet | Yodlee aggregates data from over 17,000 data sources across dozens of countries. These countries include the United States, Canada, the United Kingdom, India, Australia, South Africa, and others. Please contact our sales teams for details.

In addition to the depth and breadth of its data aggregation, Envestnet | Yodlee enriches data (known as transaction data enrichment (TDE)) through proprietary machine learning. TDE is included with data aggregation and adds metadata to enhance the value of the original transaction data. TDE-provided metadata includes expense categories, simple descriptions, merchant names, and geo-locations that can be used to develop personalized recommendations or other analytics solutions. Learn more, here.

No. Not all the endpoints are for data retrieval. Many of the endpoints are meant for authentication, control, configuration, and customer onboarding.

Envestnet | Yodlee does not provide APIs that yield financial data analytics. Application developers can build their own analytics solutions with the data provided.

A cobrand is the term used to refer to you, an Envestnet | Yodlee customer. A user is a term used to refer to the end users of your application.

Note: This information applies only to Yodlee API v1.0. Cobrand sessions have been deprecated in favor of alternative authentication/authorization protocols.

Yes, you can work with the Yodlee support team to set up dataset configuration to get all or a subset of specific datasets and attributes. Please see Working with datasets and Retrieving and Sending Datasets in FastLink Integration Guide for details.

You can override the dataset configuration at the time of adding a new provider account through FastLink.

Certain datasets are needed by default based on customers’ business needs, like BASIC_AGG_DATA.ACCOUNT_DETAILS and BASIC_AGG_DATA.STATEMENTS are configured as implicit datasets at the time of onboarding.
These datasets will be implicitly returned unless there is an override in the API request.

The developer can request access to the full account number of the user by including an http parameter ‘include=fullAccountNumber’. This feature needs to be requested in advance. When the access request is approved, the developer account will be configured to be able to place such requests.