---
title: "Enable step variants"
method: POST
path: "/v3/sequences/{id}/steps/{step_id}/enable"
tags: ["Sequence Steps"]
---

# Enable step variants

`POST /v3/sequences/{id}/steps/{step_id}/enable`

<small>_Requires the `sequences:operate` scope (or a broader one that includes it)._</small>

Enables the specified variants on a sequence step. Variants are toggled independently — failures are reported per `variantId` in the response without aborting the whole call.

## Path parameters

- `id` integer, required
- `step_id` integer, required

## Request body

- object
  - `variantIds` integer[], required — List of variant IDs to enable

## Response `200`

Dictionary keyed by variant ID. Only failed items appear; items not in the dictionary succeeded.

Possible per-item error codes:

| Error code | Meaning |
|-------|---------|
| `invalidInput` | Variant id is not valid for this step |
| `unsupportedOperation` | Step type does not support enabling/disabling variants |

- object

## Other responses

- `400` — Route/body validation failure, or a business-rule rejection.
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — User lacks required feature scope to modify this sequence
- `404` — Step not found
- `409` — Step is locked and cannot be modified
- `429` — Too Many Requests

---

[API](https://skmtc.net/reply/apis/reply-api.md) · [All operations](https://skmtc.net/reply/apis/reply-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/reply/reply-api/revisions/1c3d32eaf95e/schema)