API-Based Transactions Collection for a Specific Period
In this article, we will outline the process to run data collection (=commit), for the following parameters:
Specific internal accounts
Period (from and to date)
Specific Assets
The links to the postman contain the GraphQL query you should initiate and example responses.
Steps to Fetch Historical Balances:
1. Register the internal accounts in TRES [Link to Postman]
identifier: the address of the wallet
parentPlatform: the blockchain family (for any EVM-based - use ETHEREUM)
name: a friendly name for the wallet

2. Trigger commit [Link to Postman]
internalAccountIds: the internal account IDs you got as a response from step #1
fromDate: the start time of the data collection period, should be ISO with UTC timezone (i.e. 2025-06-14T00:00:00+00:00)
toDate: end time of the data collection period, should be ISO with UTC timezone
commitId: valid and unique UUID4 generated by the user (i.e. 80a2268a-2006-4ef2-b056-0ce134febe8f)
assetsToCollect: list of assets keys to collect, each key should be at the following format “{platform}_{identifier}”, (i.e. avax_0x9702230A8Ea53601f5cD2dc00fDBc13d4dF4A8c7 or avax_native)

3. Check Commit Status [Link to Postman]
commitId: Use the commitId you generated in step #2
The data will be completed only when the commit status is COMPLETED

4. Query Sub Transactions = Balance changing events [Link to Postman]
limit: the number of results in each page
page: the page number
timestamp_Gt: the start time of the data collection period. Same as step #2
timestamp_Lt: end time of the data collection period. Same as step #2
belongsTo_In: the internal account IDs you want to query data
asset_In: a list of asset keys to query. Same as step #2
