Update split weights
Shift traffic between the variants, and decide which of them are in the cycle at all.
Send every variant in the split exactly once, along with the revision you read. A weight of 0 excludes that variant: it stays a member and stays testable, but takes no calls, and a live variant covers its leads until it is back. Any weight from 1 puts it back in, and the weights of the live variants must total 100.
Inclusion travels with the weight rather than through its own endpoint because including an arm necessarily moves the others, and the two have to land together or the split spends a moment with something live at a share nobody chose.
Partial submissions are rejected rather than merged, both because a weight only means something relative to the others and so that a dropped variant is an error rather than a silent exclusion.
The Primary Variant cannot be excluded: it is the campaign’s own agent and the fallback for every route. At least one variant must always be live.
Required API key scope: agents:write.
Authorizations
Send your API key as Authorization: Bearer YOUR_API_KEY.
Path Parameters
Agent id of the Primary Variant. Every split operation is addressed through the primary, not through a secondary variant.
1Body
Replacement weights for every variant in the split.
Weights are replaced wholesale, not patched. Every variant in the split must appear exactly once, and the weights of the ones you keep live must total 100.
This is also how a variant is included in or excluded from the cycle. Send weight: 0 to exclude it; send any weight from 1 to include it again. Omitting a variant is an error rather than a shorthand for excluding it, so a caller that drops one by accident is refused instead of quietly taking an agent off the air.
