Using Sandbox

Using Sandbox Environment

The main goal of this quick start guide is to get you up and running as soon as possible. At the end of this quick start guide, users’ accounts and transactions can be retrieved. This is followed by step by step detailed guide.

  1. First, Register for a new developer account at Developer portal .
  2. After the registration is complete, you can link accounts and start testing. For linking accounts, 5 pre-registered test users have been provided. It can be found under Test Users section on this dashboard.
  3. Add an account for first user (or any user) by choosing Fastlink for Aggregation button on dashboard page. You could link real accounts. 
    Note – If you are testing via Fastlink and don’t want to create new dummy account, then search for DAG Site provider on Fastlink and use username(testdap.site16441.2) and password(site16441.2).
  4. Once the dummy or real account is added, Fastlink should display account summary on the last page which indicates that the account was added successfully.
  5. If you would like to retrieve the accounts and transactions of the user via APIs, please use following steps –
    1. Login using developer portal username/password on the API reference page by clicking on Set Auth Tokens. It should display cobrand and user authorization messages successfully.
    2. Under API Operations, in the section of Accounts, use /{cobrandName}/v1/accounts API to get all the accounts added by the user. For more details on specific account, use the id and container fields retrieved from the /{cobrandName}/v1/accounts API on GET Account Details API.
    3. Finally, retrieve the transactions by using Transactions API. By default, this API provides 30 days of transactions and if you would need upto 365 days of transactions, please set the fromDate and toDate in the Transactions API. Set the fromDate and toDate in Transactions API as 2013 and 2016 for Dummy Accounts.

Notes -

  1. Sometimes linking an account might take longer time as we are trying to get 365 days of transactions. Fetching 365 days of transactions can be disabled on staging or production.
  2. If the accounts are added successfully and still there are no accounts or transactions via APIs, please make sure that the same user (for which the accounts were linked) is logged in the APIs. Set the fromDate and toDate in Transactions API as 2013 and 2016 for Dummy Accounts.
  3. If there is any issue with any of the accounts, please try adding again or linking different accounts. If you need more help, please contact designated Solutions Engineer.

The complete data model is available here.

Prerequisite

The best place to start testing the Yodlee APIs for new developers is the developer portal. It’s a separate environment and can be used for testing, building prototypes or design during evaluation.

The Quick Start Guide uses the developer portal to get you up and running with APIs quickly without having to write the code. There are few important points those need to be considered while working with the portal though.

  1. Its only for testing the APIs and understanding the Data Model. It should not be used for any performance testing.

  2. No new users can be registered and existing 5 users should be used.

  3. Real accounts at financial institutions can be used for testing.

  4. There is no constant monitoring system in place as Yodlee does for staging or production environment which are available after the contract is signed.

  5. Any issues on the portal should be reported to your designated Solutions Engineer.

  6. Full account number will not be available as part of the developer portal.

  7. Developer portal users and accounts cannot be migrated to stage or production.

  8. Synchronized Data Extracts is not available on the portal.