December 01-15

Welcome to our fortnightly documentation changelog where we provide you with a detailed list of changes made to our API and documentation.

πŸŽ‰ New

  • Risk insights (open BETA)
    Our new Enrichment product is available for all users to test out. Check out our docs on how to make the most of this new resource!

  • Investment Portfolios (open BETA) and Investment Transactions (Coming soon) documentation
    Want to get an overview of your user's investments? Then look no further than our Investment Portfolios resource!


Investment Portfolios are in open BETA for everyone to use. At the moment we only support single links for the following institutions and investment products:

Bradesco Retail (Brazil)FIXED_INCOMEDEPOSIT
Santander Retail (Brazil)FIXED_INCOMEDEPOSIT

πŸ’ͺ Improved

  • As part of an ongoing documentation audit to improve our accuracy, we identified that some fields were incorrectly marked as integers when they were supposed to be floats. Now that should all be a thing of the past! But if you think you spot a mistake - just write to us at [email protected]!

  • Loan accounts now return the contract_amount field in the loan_data object
    Now, you can know what was the initial calculated cost of the loan (principal + interest + fees).

⚠️ Deprecated

  • We've removed the Accounts object from our Owners resource in order to save on duplicated information being sent. If you want to get account information for an owner, just use our Accounts resource.

  • We're removing the following fields from the loans_data object in our Accounts resource:

    • cutting_date
    • cutting_day
    • payment_due_day
    • limit_day
    • limit_date
    • no_interest_payment
    • last_payment_date
    • last_period_balance
    • next_payment_date

🐞 Fixed

  • Incorrect SDK examples for our Investment Portfolios and Investment Transactions
    Sorry about that - now you should be able to use our SDK for making calls to Invesment Portfolios without a problem.

  • Some schema examples did not show the id field in resource responses (both for 200 and 201 responses)
    Now, no matter what, we'll always return the id field for any resource. However, please remember that unless you make a request with save_data equal to true, then we will not persist the response to our database.

  • Missing fields in sandbox documentation
    We missed adding the external_id and created_at fields in our Advanced MFA flow example.