Update the strategy
| Field | Required | Description |
|---|---|---|
requestId | Yes | UUID v4 idempotency key |
positions | Yes | New allocation. Weights must sum to 10,000 bps. |
strategy.status transitions to rebalancing immediately. Positions continue to reflect current holdings until the rebalance completes.
What happens during a strategy update
Strategy updates are asynchronous and may require Turnkey approval:- The new target weights are saved immediately and reflected in the wallet response.
- A Turnkey approval may be required before rebalancing begins.
- The system plans a rebalance (sells → buys → bridges as needed).
- The rebalance executes over time. For positions with longer unwind windows (e.g.
rlpatPT24H), the full rebalance can take hours.
Strategy statuses
There are two distinct status concepts:Wallet-level strategy.status
The wallet response includes strategy.status reflecting current holdings vs. targets:
| Status | Meaning |
|---|---|
aligned | Holdings match target weights (within tolerance) |
rebalancing | Actively rebalancing to reach targets |
Webhook strategy update status
Theportfolio_wallet.strategy.status_changed webhook tracks the lifecycle of a specific strategy update operation:
| Status | Meaning |
|---|---|
pending_approval | Waiting for Turnkey approval |
processing | Rebalance in progress |
completed | Strategy update fully applied |
failed | Strategy update failed |
strategy.status is a point-in-time snapshot of the wallet, while the webhook status tracks the update operation itself.
Strategy webhook
Strategy updates emitportfolio_wallet.strategy.status_changed events. See Webhooks.
Next steps
- Balances and Yield — monitor positions as the rebalance executes
- Yield Sources — explore sources and quote a new strategy
- Transaction Approvals — approve rebalance transactions via Turnkey