How Awaken works
The shared data flow behind consumer automation and embedded tax products.
From accounts to reports
A client is the tax workspace. Accounts connect wallets and exchanges to that workspace. Imports normalize activity into transactions, then the tax engine recalculates the ledger. Taxable events and reports are derived from that ledger.
1. Client
The tax workspace owns settings, accounts, transactions, and reports.
2. Accounts
Wallets and exchanges import activity into the workspace.
3. Import
Awaken fetches and normalizes raw activity. Account sync jobs expose progress.
4. Recalculate
The engine rebuilds transfers, cost basis, gains, and income.
5. Read or export
Consume transactions, tax previews, and downloadable reports.
The same objects everywhere
GraphQL uses camelCase while the partner REST API includes some snake_case job fields, but both surfaces operate on the same underlying client, account, transaction, and report model.
After imports or transaction edits, wait for the active recalculation job to finish before reading final tax totals.