An operation represents one cycle of work against a strategy — an enrollment (initial onboarding of a participant), a top_up (additional funding into an already-enrolled strategy), or a partial_sell (selling part of an enrolled trader's crypto holdings back to fiat). This webhook fires on every state transition of that operation.
Parameter
Description
Type
id
Unique identifier for this operation.
string (UUID)
strategy_id
Identifier of the strategy this operation belongs to.
string (UUID)
request_id
Idempotency key from the client request that created this operation.
string (UUID)
type
Kind of operation. One of enrollment, top_up, partial_sell.
Machine-readable reason for the current status. Empty when not applicable. See Operation status reasons.
string
allocations
Array of {underlying_currency, weight} entries describing the target asset mix for this operation. Weights are strings carrying decimal values that sum to 1.
array
created_at
Operation creation timestamp (UTC, RFC3339).
string
updated_at
Timestamp of the transition that triggered this webhook (UTC, RFC3339).
Quotes are being requested for the configured allocations.
settling
Quotes accepted, underlying trades and balance movements are being applied.
settled
Operation completed successfully and balances are reflected on the strategy account.
skipped
Operation completed without performing any work. (Planned — fires once the rebalance / dust-skip flow lands; current operations do not produce this status.)
failed
Operation did not complete. Check status_reason for details.
Operation status reasons
Reason
Description
no_executions
Operation ended without producing any executions.
all_rejected
Every underlying execution was rejected — see the corresponding execution webhook for the per-execution reason. Operation status is failed.
all_skipped
Every underlying execution ended skipped. Operation status is skipped. (Planned — fires once the rebalance / dust-skip flow lands.)
partial_success
Mixed outcome — at least one execution settled and at least one was rejected. Operation status is settled (not failed) with this reason; inspect each execution webhook for the per-participant outcome.