PATCH
Edit an A/B arm

Authorizations

Authorization
string
header
required

A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.

Headers

Idempotency-Key
string
required

A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.

Path Parameters

campaignId
string
required
variantId
string
required

Body

application/json

Every field is optional and an omitted one keeps its stored value. That is why this is a PATCH: a full replace that only adjusted a weight would blank the arm's subject and body, and the share of the audience assigned to it would receive an empty message while the other arms sent correctly.

variant_key
string

Still unique per campaign; a clash is 409 variant_key_taken.

subject
string
body
string
weight
integer

At least 1. See the create for why an explicit 0 is refused.

Response

Success

data
object