Yodlee provides realistic test data for use in the sandbox environment. You can use the test data to put your app through its paces with a variety of situations close to real world accounts. The sandbox does not support linking to live data (real world accounts), so we simulate this with a set of fictional financial institutions. Each institution has one or more customer login accounts. Each customer login account accesses one or more simulated accounts with that institution (checking account, savings account, credit card account, etc). We provide the (simulated) login credentials to link or verify an account using FastLink. Connecting an account with FastLink is an idempotent operation - you can repeat it without harm.
FastLink Some Accounts for a Test User
In the sandbox environment we provide 5 test users, already registered. You cannot register new users in the sandbox. For any of your test users, you can link the test accounts provided by following these steps.
-
Select one test user. The test user names are shown on your dashboard page when you click the "View test users" button. For example, you might choose a test user with the test user name sbMem5c758c82bb1d11. This id is not known to the banks, and doesn't appear in bank data - which gives us the flexibility to link any of the test accounts in the table below with any of the 5 test users.
-
Click the "Launch FastLink" button next to that user's Test User Name on the dashboard page. This launches the FastLink tool, allowing you to link any of the test accounts shown below.
-
Choose a link scenario from the table below, for example "plain login with 5 user accounts"
-
In FastLink, click the "magnifying glass" icon and search for the "bank" name shown for this test scenario. An example bank name is "DAG Site". Look for an exact match of name, as we have several close variants. Select the site with the exact name match.
-
When prompted, enter the user name and password shown in the table for that site.
-
If the test scenario includes Multi-Factor Authentication (MFA), provide the responses shown in the MFA column, within the time limit indicated.
-
Click "Submit" to send the account login information to FastLink
That's all there is to it. FastLink will read the test account details, and store the data for this test user into Yodlee's secure database, ready for your app to read with API calls.
| FastLink scenario | Bank Name to search for in FastLink |
User name, password to use in FastLink |
Multi-Factor Authentication response |
|---|---|---|---|
| plain login with 2 accounts (checking, savings) | DAG Site | YodTest.site16441.1, site16441.1 |
not applicable |
| plain login with 5 accounts (checking, savings, credit cards, loans, brokerage) | DAG Site | YodTest.site16441.2, site16441.2 |
not applicable |
| login with security questions | DAG Site SecurityQA | YodTest.site16486.1, site16486.1 |
Answer Texas to state question Answer w3schools to school question |
| login with one time password (sent to phone/email for real world accounts, but we simply give the code to you in this table). | DAG Site Multilevel | YodTest.site16442.1, site16442.1 |
Answer 123456 to password question |
You will probably find it helpful to review our Data Model page. The page explains the data objects accessible through the Yodlee API, and how they are connected to each other. We use the term "data model" to be synonymous with "data structure". Some of these models are returned by certain API calls. Other calls return selected data from the objects. Once you have linked some of these accounts to some of the test users, Yodlee will serve your app with the relevant data when you make API calls. That's where your app testing really starts.
Answers to Frequently-Asked Questions
Q. What happens if you click on the gear icon in FastLink, and delete one of these test accounts?
A. All account-related data for that test account will be deleted, and you won't be able to use the account for further testing. We recommend you not delete test accounts.
Q. What data is in each of these test accounts?
A. Use API calls, either in your code, or by making calls from the API reference page to review the data. A call to GET providerAccounts will bring in data on all the accounts that a test user has with that financial institution. The providerId is listed in the table below, for convenience. A financial institution is called a "provider" in Yodlee terminology because they provide accounts to end users. The providerId is a unique Id assigned to each provider by Yodlee. End users generally have one online account with a provider, and that one username/password allows them to access all their financial accounts (credit card, checking, savings, etc). providerAccount holds details of that one top level account.
Q. Where do I get providerIds when I am not working in the sandbox?
A. FastLink returns a number of parameters, one of which is the providerId for the institution providing the account that you just linked. You'll be able to see that when you test with Postman. Look for the Postman "card" in Tools section of this page.
Q. Can I link the same account with more than one user?
A. That's not a common event in the real world. For the purpose of testing, both users would be associated with that test data. The accounts are not merged in any manner. It is preferred to avoid confusing data.
Q. What does DAG mean?
A. It's an abbreviation for Dummy Account Generator. Behind the scenes, new test data can be created using XML files. You may do that if your testing needs exceed the small amount of data we have prepared for you. The better alternative is to move to the Launch pricing tier and link live accounts. The Launch tier is free for modest amounts of activity.
Q. What are all the other providers that start with "DAG" that I see when I search for a provider in FastLink?
A. Those are additional fictitious providers which implement other test cases. Please use the test data outlined on this page to test account verification flows.
ProviderId Table
Here are the providerIds associated with the test data. This data is needed for some API calls.
| Bank Name | providerId |
|---|---|
| DAG Site | 16441 |
| DAG Site SecurityQA | 16486 |
| DAG Site Multilevel | 16442 |
You are now ready to test verification flow in the sandbox.