This topic will be updated throughout the quarter as we improve the product. For a complete overview of all Totogi releases, visit the Release Notes Archive.
Additionally, to stay ahead of future releases, check out Upcoming Changes . This topic provides detailed information on expected changes, helping you to plan and adapt your systems and integrations effectively.
New Functionality
- -
Changed Functionality
-
Mar 13, 2026 Totogi now supports AWS External ID when assuming cross-account IAM roles used for exporting provider data to customer AWS accounts. Each provider is assigned a unique External ID that Totogi includes when assuming the configured export role. This follows AWS security best practices to prevent unauthorized role assumption and ensure that only requests originating from Totogi for your provider can access the export role.
External ID is available to tenant administrators through the GetMyProviderConfig API. Export operations remain fully backward compatible, existing IAM roles without an External ID condition will continue to work. Customers can optionally configure the External ID condition in their IAM role trust policy for enhanced security.
For step-by-step instructions on retrieving your External ID and configuring your IAM role, see How to Configure AWS External ID for Totogi Data Exports.
Fixes and Improvements
-
Feb 09, 2026 Totogi has enhanced the GraphQL balance management APIs to support batch operations for creating, updating, and deleting balances. The
createBalance,updateBalance, anddeleteBalancemutations now accept an array, allowing multiple balances to be processed in a single API call. This simplifies integrations and improves efficiency by removing the need to perform balance operations one by one. Existing singular fields remain supported for backward compatibility but are planned for deprecation in May 2026.
Customers are encouraged to adopt the batch-based approach to avoid any impact once the singular fields are deprecated.
Ozlem Gok
Comments