Token features API
Reference index for the eleven DALP token features and the Platform API endpoints that configure and operate them during asset creation and servicing.
DALP exposes eleven token features that instrument templates attach to a new asset. You configure each one at deployment through the token-creation endpoint and operate it afterward through feature-specific routes or the asset-detail endpoints in the same group.
Here you find the developer reference for those routes. Operator how-tos live under operators/token-features. The design model for each feature lives under architects/components/token-features.
Feature catalog
Each row links to the developer reference, the architecture explanation, and the operator how-to for that feature.
| 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. It reads the template's requiredFeatures, applies the template defaults, and overlays any operator-supplied configs. It then checks dependency and incompatibility rules per feature constraints and submits the resulting feature set at 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
Read the current configuration and live values 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
Parameters that governance controls 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). Each update lands as an async blockchain mutation.
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.
User asset balances API
List the authenticated participant's token holdings through the DALP API, aggregated across their linked wallets, with balances, base-currency value, and yield denomination details.
historical-balances feature API reference
API reference for reading DALP historical-balances checkpoints, including the timestamp timepoint model and the holder-history endpoints used by integrations.