# Voting Power

Source: https://docs.settlemint.com/docs/api-reference/token-features/voting-power
API reference for the DALP Voting Power token feature, including delegation mutations, delegation history, and current distribution reads.



The Voting Power feature exposes each token holder's delegated governance weight on chain.

Use this page when you need API paths for direct or relayed delegations, delegation history, or the current weight distribution. For the product model, see [Voting Power architecture](/docs/architects/components/token-features/voting-power). For operator steps, see [Voting Power how-to](/docs/operators/token-features/voting-power).

## Configuration [#configuration]

No `featureConfigs` entry is required. `voting-power` is the API identifier for this feature. It accepts no feature-specific settings at token creation time. You can omit it from `featureConfigs` entirely, or pass an empty object.

## Mutations [#mutations]

| Endpoint                                                                            | Body                                                                                                  | Returns                                                      |
| ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| `POST /api/v2/tokens/{tokenAddress}/features/voting-power/delegations`              | `{ "delegatee": "0x..." }`                                                                            | An async blockchain mutation response for the updated token. |
| `POST /api/v2/tokens/{tokenAddress}/features/voting-power/delegations/by-signature` | `{ "delegatee": "0x...", "nonce": "0", "expiry": "1767225600", "v": 27, "r": "0x...", "s": "0x..." }` | An async blockchain mutation response for the updated token. |

A direct delegation uses the selected wallet, which must be registered in the token identity registry. The signature-based path relays signed data; the Platform API validates the signer before queuing the transaction.

## Reads [#reads]

| Endpoint                                                      | Returns                                                                                                                                   |
| ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| `GET /api/v2/tokens/{tokenAddress}/voting-delegations`        | Paginated delegation lifecycle rows for Voting Power.                                                                                     |
| `GET /api/v2/tokens/{tokenAddress}/voting-power/distribution` | Current voting power per delegate, ordered by latest votes, with a top-N list and an aggregated `other` bucket for the remaining holders. |

To query holder balances at a snapshot timepoint, use the `historical-balances` endpoints. The two features answer different questions: Voting Power tracks delegated governance weight, while Historical Balances tracks token balances and total supply over time.

## Related [#related]

* [Historical Balances](/docs/api-reference/token-features/historical-balances): balance checkpoints and snapshot reads.
* [Voting Power architecture](/docs/architects/components/token-features/voting-power): the feature model and constraints.
* [Voting Power how-to](/docs/operators/token-features/voting-power): operator workflow steps.