# historical-balances

Source: https://docs.settlemint.com/docs/developers/api-integration/token-features/historical-balances
API reference for the DALP historical-balances token feature, attached automatically by most instrument templates without operator input.



The `historical-balances` token feature records a balance checkpoint for every holder at every block where their balance changes. It attaches without operator input on almost every instrument template.

For the operator how-to, see [Historical balances how-to](/docs/operators/token-features/historical-balances). For the architecture model, see [Historical balances architecture](/docs/architects/components/token-features/historical-balances).

## Configuration [#configuration]

No `featureConfigs` entry required. The feature is self-contained and attaches when the selected template lists it in `requiredFeatures`.

## Reading snapshot data [#reading-snapshot-data]

Use the token holders-and-transfers endpoints to read balance history.

| Endpoint                                                 | Returns                                     |
| -------------------------------------------------------- | ------------------------------------------- |
| `GET /api/v2/token/{address}/holders`                    | Current holder list and balances.           |
| `GET /api/v2/token/{address}/holders/{holder}/history`   | Balance checkpoints for a holder.           |
| `GET /api/v2/token/{address}/balance-at-block?block={n}` | Balances for the asset at a specific block. |

See [Token holders and transfers](/docs/developers/api-integration/tokens/token-holders-transfers) for the full contract.

## Related [#related]

* [Voting power](/docs/developers/api-integration/token-features/voting-power) — uses historical-balances for snapshot weights.
* [Feature constraints](/docs/architects/components/token-features/feature-constraints)