# Delete Sequence Variant

> Delete an A/B variant. The campaign must not be active.

Requires an API key with the `write` scope.

When the step has two variants, deleting one also deletes the other: a step with a single variant goes back to its own subject and body. The call does not say which variants were removed; list the variants afterwards if you need to know.

## Path Parameters

<ParamField path="campaign_id" type="string" required>The campaign.</ParamField>
<ParamField path="sequence_id" type="string" required>The sequence step.</ParamField>
<ParamField path="variant_id" type="string" required>The variant.</ParamField>

## Response

<ResponseField name="data" type="object">
  <Expandable title="data">
    <ResponseField name="id" type="string">The variant you asked to delete.</ResponseField>
    <ResponseField name="deleted" type="boolean">`true`.</ResponseField>
  </Expandable>
</ResponseField>

<RequestExample>
```bash cURL
curl -X DELETE "https://api.foxreach.io/api/v1/campaigns/cmcamp1/sequences/cmseq1/variants/cmvar1" \
  -H "X-API-Key: otr_your_key"
```

```python Python SDK
from foxreach import FoxReach

client = FoxReach(api_key="otr_your_key")
client.campaigns.sequences.delete_variant("cmcamp1", "cmseq1", "cmvar1")
```

```typescript TypeScript SDK
import { FoxReach } from "foxreach";

const client = new FoxReach({ apiKey: "otr_your_key" });
await client.campaigns.sequences.deleteVariant("cmcamp1", "cmseq1", "cmvar1");
```
</RequestExample>

<ResponseExample>
```json
{
  "data": { "id": "cmvar1", "deleted": true }
}
```
</ResponseExample>

## Errors

| Status | Description |
|--------|-------------|
| `401` | Missing, invalid, revoked or expired API key |
| `403` | API key does not have the required scope: `write` |
| `400` | The campaign is active (pause it first) |
| `404` | Campaign, sequence step or variant not found in this workspace |

## Rate Limit

- **120 requests per minute, shared by every `write` call in your workspace.** Fixed 60-second window.
- Every response includes `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Reset` (unix epoch seconds) and `X-RateLimit-Bucket` (`write`).
- A `429` response includes a `Retry-After` header (seconds until the bucket resets).

For client-side patterns (`Retry-After`, exponential backoff, monitoring `X-RateLimit-Remaining`), see [Rate Limiting](/rate-limiting).