> ## 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.

# Transactions

> Read an account's full activity history, filter it by type, status, and date, and reconcile it against balances.

Every balance change on an account is a transaction: deposits, withdrawals, trades, fees, and transfers. Use the feed to show a customer their activity, to drive your own ledger, to reconcile against balances, and to feed reporting. Each transaction lists the entries behind it, so you can see exactly which account and asset moved, in which direction.

## What's available

| Action | Status | Notes |
| :- | :- | :- |
| List transactions | Live | |
| Funding allocations | Under construction | Returns mocked data only |

## The transaction model

A transaction has three parts:

1. **What happened**: a `transactionType` and a `status`.
2. **When**: `createdAt`, and `endedAt` once the transaction reaches a final state.
3. **Whose balances moved**: a list of entries (the `subaccounts` field), each naming an `accountId`, an `assetType`, an `amount`, a `balanceType`, and a `direction` (`CREDIT` for funds in, `DEBIT` for funds out). `balanceType` is `AVAILABLE` for a settled movement, `HOLD` for an amount set aside for an in-flight debit, or `PENDING` for a credit not yet settled. Only `AVAILABLE` entries change the `TOTAL` balance.

One transaction can carry several entries. A trade debits one asset and credits another. An order allocated across accounts touches each of them. Summing the entries per account and asset is how you reconcile the feed against [balances](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-balances.md).

### Transaction types

| Category | Types |
| :- | :- |
| Money movement | `DEPOSIT` (funds in), `WITHDRAWAL` (funds out), `RETURN` (a returned deposit or withdrawal), `SUBACCOUNT_TRANSFER` (a transfer between accounts in your organization), `DEPOSIT_SWEEP` (a deposit moved from its deposit address into pooled custody) |
| Trading | `TRADE` (the execution), `TRADE_SETTLEMENT` (the settlement of its legs) |
| Fees | `MANAGEMENT_FEE`, `CUSTODY_FEE`, `ADVISORY_FEE`, `MODEL_FEE`, `TRANSACTION_FEE`, `FEE_SETTLEMENT` (a fee collected), `GAS_FILL` (network fee funding) |
| Staking | `STAKE`, `UNSTAKE`, `CLAIM`, `STAKING_REWARD`, `DELEGATION_REWARD`. Listed for completeness; staking isn't offered through the v4 API today. |

### Statuses

| Status | Meaning |
| :- | :- |
| `PENDING` | In progress. Funds are held until the transaction posts or is canceled. |
| `POSTED` | Complete, and for on-chain movements, confirmed on the blockchain |
| `CANCELED` | Funds weren't moved |

`endedAt` is set when the transaction reaches `POSTED` or `CANCELED`, and absent while it's `PENDING`. On-chain deposits and withdrawals also carry `transactionHash`, the blockchain transaction hash, once settled.

***

## Integration steps

### Step 1: List transactions

**`GET /v4/accounts/{accountId}/transactions`**

Returns the account's transactions, most recent first. Page with `limit` and `after`.

| Parameter | Description |
| :- | :- |
| `types` | One or more transaction types, comma-separated |
| `statuses` | One or more of `POSTED`, `PENDING`, `CANCELED` |
| `transactionIds` | Specific transactions, comma-separated |
| `startDate`, `endDate` | Inclusive date range, `YYYY-MM-DD` in UTC. The earliest valid date is `2017-01-01`. |

```bash Request theme={null}
curl --request GET \
     --url 'https://api.anchorage-staging.com/v4/accounts/cb80459c-a930-444e-8f17-69ba9d0e122f/transactions?types=DEPOSIT,WITHDRAWAL&statuses=POSTED,PENDING&startDate=2026-11-01&limit=50' \
     --header 'Api-Access-Key: {API Key}' \
     --header 'accept: application/json'
```

```json Response (200) theme={null}
{
  "data": [
    {
      "transactionId": "c4c4652f0c07472ca7f8955fbe07775d",
      "transactionType": "DEPOSIT",
      "status": "PENDING",
      "subaccounts": [
        {
          "accountId": "cb80459c-a930-444e-8f17-69ba9d0e122f",
          "assetType": "BTC",
          "amount": "0.5",
          "balanceType": "AVAILABLE",
          "direction": "CREDIT"
        }
      ],
      "createdAt": "2026-11-04T12:34:56.000Z",
      "endedAt": null,
      "transactionHash": "3a1f0c9e7b2d4f6a8c0e1b3d5f7a9c2e4b6d8f0a1c3e5b7d9f1a3c5e7b9d1f3a"
    },
    {
      "transactionId": "9b8a7c6d5e4f4a3b8c2d1e0f9a8b7c6d",
      "transactionType": "WITHDRAWAL",
      "status": "POSTED",
      "subaccounts": [
        {
          "accountId": "cb80459c-a930-444e-8f17-69ba9d0e122f",
          "assetType": "USD",
          "amount": "5000.00",
          "balanceType": "AVAILABLE",
          "direction": "DEBIT"
        }
      ],
      "createdAt": "2026-11-03T09:15:00.000Z",
      "endedAt": "2026-11-03T09:20:12.000Z",
      "transactionHash": null
    }
  ],
  "page": {
    "endCursor": "eyJjcmVhdGVkQXQiOiIyMDI2LTExLTAzVDA5OjE1OjAwWiJ9"
  }
}
```

A [withdrawal](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-withdrawals.md) carries the `transactionId` of its `WITHDRAWAL` transaction, and a [deposit attribution](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-deposits-crypto.md) is keyed by its `DEPOSIT` transaction ID. Pass either as `transactionIds` to pull the matching entry.

For a daily, file-based reconciliation of positions and activity, see [Reconciliation files](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-reconciliation-files.md).

> [!NOTE]
>
> For an ongoing sync, poll with `startDate` set to your last sync point and re-check `PENDING` transactions until they reach `POSTED` or `CANCELED`. A transaction's `status` and `endedAt` change after it first appears.

### Step 2: Allocate funding

**Under construction.** `GET` and `POST /v4/accounts/{accountId}/transactions/allocations` are in the reference for allocating pre-funded USD between a funding account and customer accounts, but they return mocked data only today. This section will be updated when the endpoints are available for testing.


## Related topics

- [List transactions](https://docs.anchorage.com/knowledge-base/porto/api-reference/v2/transactions/list-transactions.md)
- [Reject a transaction](https://docs.anchorage.com/knowledge-base/api-reference/v2/transactions/reject-a-transaction.md)
- [List Transactions](https://docs.anchorage.com/knowledge-base/porto/api-reference/v2/tax/list-transactions.md)
- [List all transactions](https://docs.anchorage.com/knowledge-base/api-reference/v4/transactions/list-all-transactions.md)
