Token features API
Reference index for the eleven DALP token features and the dapi endpoints that configure and operate them during asset creation and servicing.
DALP exposes eleven token features that instrument templates attach to a new asset. Configuring a feature during deployment happens through the standard token-creation route in kit/dapi/src/routes/token/. Operating a feature after deployment uses feature-specific endpoints or the asset-detail endpoints under the same route group.
This section is the developer reference for those endpoints. Operator how-tos for the same features live under operators/token-features. The architecture model for each feature lives under architects/components/token-features.
Feature catalog
| Feature | Configurable parameters | Architecture | Operator how-to |
|---|---|---|---|
| historical-balances | None | Architecture | How-to |
| maturity-redemption | maturityDate, denominationAsset, treasury, faceValue | Architecture | How-to |
| fixed-treasury-yield | rate, interval, treasury, denominationAsset | Architecture | How-to |
| voting-power | None | Architecture | How-to |
| aum-fee | feeBps, recipient | Architecture | How-to |
| transaction-fee | mintFeeBps, burnFeeBps, transferFeeBps, recipient | Architecture | How-to |
| transaction-fee-accounting | mintFeeBps, burnFeeBps, transferFeeBps, recipient | Architecture | How-to |
| external-transaction-fee | feeToken, mintFeeAmount, burnFeeAmount, transferFeeAmount, recipient | Architecture | How-to |
| conversion | targetToken, conversionMinter, denominationAsset, discountBps, capPricePerShareWad, conversionWindowStart/End, minConversionAmount, partialAllowed | Architecture | How-to |
| conversion-minter | None (companion to conversion) | Architecture | How-to |
| permit | None | Architecture | How-to |
How features attach via the API
The token-creation route accepts a templateId and an optional featureConfigs map. The route reads the template's requiredFeatures, applies the template defaults, overlays any operator-supplied configurations, validates dependency and incompatibility rules per feature constraints, and submits the resulting feature set during deployment.
POST /api/v2/token
Content-Type: application/json
Prefer: respond-async
{
"templateId": "system-bond",
"name": "Acme Corporate Bond 2025",
"symbol": "ACME25",
"decimals": 18,
"featureConfigs": {
"fixed-treasury-yield": {
"rate": 500,
"interval": "DAILY",
"treasury": "0x...",
"denominationAsset": "0x..."
},
"maturity-redemption": {
"maturityDate": "2027-12-31",
"denominationAsset": "0x...",
"treasury": "0x...",
"faceValue": "1000.00"
}
}
}The response is the standard async blockchain-mutation envelope. See Token lifecycle for the full token-creation contract.
Reading feature state
Feature state reads through the token-detail endpoints:
| Endpoint | Returns |
|---|---|
GET /api/v2/token/{address} | Token record including attached features and their current parameter values. |
GET /api/v2/token/{address}/features | List of attached features and their configuration. |
| Feature-specific endpoints documented per page below. | Feature-specific state and operations (e.g., accrued yield, AUM-fee accrual, conversion window). |
Updating feature parameters
Restricted-mutable parameters update through the governance-update path. Most feature pages document the specific endpoint (typically PUT /api/v2/token/{address}/features/{featureId} with the parameter delta). Updates land as async blockchain mutations.
Read next
- Token lifecycle for the full token-creation contract.
- Feature constraints for the dependency and incompatibility rules.
- System templates catalog for the template-to-feature mapping.