Skip to main content
PUT
Update a step variant

Authorizations

Authorization
string
header
required

Authenticate every request with a Bearer token. Pass your Reply API key in the Authorization header:

Get your API key from the Reply dashboard: Settings → API Key.

Path Parameters

id
integer
required

Sequence Id

step_id
integer
required

Step Id

variant_id
integer
required

Variant Id

Body

Request body for creating or updating a text variant

message
string
required

Message content of the variant. Variable names are case-sensitive, for example {{FirstName}}. See GET /v3/email-templates/variables for the full list. In email steps, unknown variables are rejected with 400.

subject
string | null

Subject line of the variant. Variable names are case-sensitive, for example {{FirstName}}. See GET /v3/email-templates/variables for the full list. In email steps, unknown variables are rejected with 400.

isEnabled
boolean
default:true

Whether the variant is enabled

attachmentIds
integer[] | null

IDs of previously uploaded attachments to attach to this variant. Upload files via POST /v3/attachments first to obtain attachment IDs. A variant may carry up to 3 attachments. Omit or pass null to leave attachments unchanged on update; pass an empty array to clear existing attachments.

Maximum array length: 3

Response

Variant updated successfully

A text variant for a sequence step

id
integer
read-only

Unique identifier for the variant

letter
string
read-only

Label of the variant as shown in the app: A, B, C, … by the variant's position in id order within the step, disabled variants included. After Z the letters repeat with a number (A1, B1, …). The label is positional, so deleting a variant relabels the variants after it; use id to identify a variant.

subject
string | null

Subject line of the variant

message
string | null

Message content of the variant

isEnabled
boolean

Whether the variant is enabled

hasAttachments
boolean

Whether the variant has any attachments. To retrieve or modify attachments, use GET /v3/attachments and the attachmentIds field on create/update. For a LinkedIn voice message step, true when the variant holds a recording.