sequences
Update a step variant for a sequence
Update the <code>payload</code>, <code>status</code>, <code>taskNote</code>, <code>priority</code>, <code>assigneeId</code>, or <code>attachmentIds</code> of an existing variant. The <code>payload</code> shape must match the step's channel (see OpenAPI.md).
patch/v1/sequences/{sequenceId}/steps/{stepId}/variants/{variantId}
Request
- Base URLhttps://developer.saleshandy.com (the document declares no server; this is the origin it was published from)
- AuthAPI key in header x-api-key
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
sequenceIdstring required
The ID of the sequence
stepIdstring required
The ID of the step
variantIdstring required
The ID of the variant
Request body
Example request
{
"status": 1,
"taskNote": "Follow up within 24 hours if no reply",
"payload": {
"subject": "Following up, {{firstName}}",
"content": "<p>Hi {{firstName}},</p><p>Wanted to follow up on my last email.</p>",
"preheader": "Following up"
},
"absoluteDays": 3,
"attachmentIds": [
"lN5xKp2vJq",
"aQ8dVzYw1R"
],
"assigneeId": "z6R8Mw4vBn"
}Response
Sequence step variant updated successfully
unknown required
Example response
{
"message": "Sequence step variant updated successfully",
"payload": 1
}Changes
No recorded changes to this operation across all 4 revisions of this API.