> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anchorage.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reporting overview

> Choose how to report on balances, transactions, and sensitive operations through the API or the web dashboard.

Reconcile balances and transactions through the v2 API with `GET /v2/wallets` and `GET /v2/transactions`. Sensitive operations, such as role changes and IP allowlist edits, don't have a reporting API yet, so report on them from the web dashboard.

| What you're reporting on | Where | Status |
| :- | :- | :- |
| Wallet balances | `GET /v2/wallets` | Available |
| Deposits, withdrawals, transfers, and rewards | `GET /v2/transactions` | Available |
| Operations and roles | Web dashboard | Available |
| IP allowlist changes | Web dashboard | In development |
| Organization-wide audit events | `GET /v2/audit-events` | In development |

## Reconcile balances

[`GET /v2/wallets`](/knowledge-base/api-reference/v2/wallets/list-all-wallets-for-all-vaults) lists every wallet your API key can read, across all vaults, with a balance for each asset the wallet holds. To read a single wallet, use [`GET /v2/wallets/{walletId}`](/knowledge-base/api-reference/v2/wallets/wallet-details-for-a-wallet). Both need the **Read vault activity** permission.

Each balance is an object with `quantity`, `currentPrice`, and `currentUSDValue`:

| Field | What it holds |
| :- | :- |
| `totalBalance` | The wallet's total holdings of the asset |
| `availableBalance` | Funds you can move now, after holds for pending operations, compliance review, API-placed holds, and vesting |
| `stakedBalance` | Principal currently staked |
| `unclaimedBalance` | Staking rewards earned but not yet claimed |

Don't expect the other balances to sum to `totalBalance`. Whether staked or unbonding funds are folded into `totalBalance` depends on the network.

Narrow the list with `assetType`, `networkId`, `subaccountIds`, and `filterByIsArchived`. Pass `minUsdValue=0` to skip wallets that hold nothing. Set `limit` to return up to 100 wallets per page (default 25), and follow `page.next` for the next page. See [Pagination](/knowledge-base/api-reference/errors-pagination#pagination).

`GET /v2/wallets` returns balances as of the request and has no date parameter. To keep a balance history, store each response, or download daily balance reports from the web dashboard's [Reporting](/knowledge-base/platform/users/web-dashboard/reporting) section. For what each dashboard balance label means, see [Reading balances](/knowledge-base/platform/users/web-dashboard/reading-balances).

## Reconcile transactions

[`GET /v2/transactions`](/knowledge-base/api-reference/v2/transactions/list-transactions) lists transactions across the vaults your API key can read, and needs the **Read vault activity** permission. Use these filters to scope a reconciliation run:

| Parameter | Use |
| :- | :- |
| `startDate`, `endDate` | Inclusive UTC dates in `YYYY-MM-DD` format, matched against when the transaction succeeded or failed |
| `vaultId`, `walletId` | Limit results to one vault or one wallet |
| `types` | Comma-separated types, such as `DEPOSIT,WITHDRAW,TRANSFER,STAKING_REWARD` |
| `destinationAddress` | Limit results to one receiving address |

Pagination works the same way as `GET /v2/wallets`. To fetch one record, use `GET /v2/transactions/{transactionId}`.

`amount.quantity` and `fee.quantity` are signed relative to the wallet the record belongs to. Deposits are positive. Withdrawals, outgoing transfers, and fees are negative. Sum them as returned, without flipping signs by `transactionType`, to reproduce a wallet's balance over a period.

The price and USD values on a transaction are recent but not real-time. For status lifecycles, webhooks, and telling internal deposits from external ones, see [Track movement status](/knowledge-base/platform/developers/move-money/operate/track-status).

## Report on sensitive operations

Report on approvals, access, and security settings from the web dashboard:

* [Operations](/knowledge-base/platform/users/web-dashboard/operations) lists pending and past operations across your organization. Filter by type, date range, or status, then download the results.
* [Roles](/knowledge-base/platform/users/web-dashboard/team-policies#roles) exports each user's roles and permissions when you select **Download structure**.
* The [IP allowlist audit log](/knowledge-base/platform/users/ip-allowlist#review-the-audit-log) records every allowlist change, with who made it and when.
* [Reporting](/knowledge-base/platform/users/web-dashboard/reporting) holds monthly statements and balance and transaction reports, which you can download or schedule.

## Audit trail API

[Audit trail via API](/knowledge-base/platform/developers/reporting/audit-trail) describes `GET /v2/audit-events`, a feed of audit events such as sign-ins, approvals, and exports, built for SIEM ingestion. It's in development, so use the web dashboard reports above until it's generally available.


## Related topics

- [Audit trail via API](/knowledge-base/platform/developers/reporting/audit-trail.md)
- [Overview](/knowledge-base/platform/developers/etf/etf-overview.md)