🎉 New:
Added new trade_settle_ind field in Source Transactions API — this is an indicator to declare if the transaction records provided by the custodian is a trade or settlement date based. This field is filterable so you are able to retrieve transactions records from BridgeFT with the type required for your use case: T = Trade Date Based, S = Settlement Date Based.
...Click here to view more updates...

🛠 Fixes & Improvements:
We improved POST requests validation across the platform and enhanced the error messages returned in case of any incorrect requests being sent to our platform. This should help to more easily troubleshoot client-side errors and ensure the appropriate usage of our platform.
...Click here to view more updates...

🎉 New:
Exchange SSN / Tax ID Token endpoint — allows you to convert encrypted SSN / Tax ID token(s) to the initial value(s) in plain text format. Please take note that PII security measures apply, and additional authorization is required to use this endpoint. For more details, please refer to the SSN / Tax ID Conversion Guide.
...Click here to view more updates...

🎉 New:
Source Transactions API - allows you to retrieve the detailed transactional information in addition to existing Source Lots, Positions, RGLs and Balances. The first version of this API provides the main fields and we are working to supplying more detailed data going forward. Please refer to the Transactions Data Schema document for more details.
... Click here to view more updates...

🎉 New:
Related Persons API - is a new component of the Accounts Management toolbox, enabling you to retrieve information about all related persons in addition to the account details accessible via the Accounts API. This is released as “beta” version supporting Pershing custodian. We will be gradually expanding this functionality to cover all custodians. Please refer to the Related Persons Guide for more details.
... Click here to view more updates...

🎉 New:
Our API Versioning approach has been changed from the traditional numeric versioning scheme (e.g. 1.0.0) to a more informative date-based versioning system. Our previous main v2.6.0 now is automatically defaulted to v2023.1. There is no service disruption and no any actions are required from you now!
For more details please visit API Versioning Overview and How to Consume New Versions pages in documentation.
... Click here to view more updates...