# PATCH /sequences/{id}/status

Part of the SendHeron REST API. Base URL: `https://api.sendheron.com/api/v1`

Activate or pause a sequence.

```http
PATCH https://api.sendheron.com/api/v1/sequences/{id}/status
Authorization: Bearer <YOUR_API_KEY>
```

**Required scopes:** `sequences:write`

**Success status:** `200`

**Rate limit:** 100/min per key, counted against the organization's SEND ceiling (200/min).

**Path parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | uuid | yes | Sequence UUID. |

**Body parameters**

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `status` | ACTIVE \| PAUSED | yes | `DRAFT` is deliberately not accepted: returning an active sequence to draft would strand the enrollments already running through it. |

> Activation is refused unless the graph is sound: at least one step, a trigger, no orphaned steps, and every step configured well enough to run. Pausing keeps each enrolled contact exactly where it stands, so activating again continues rather than restarts. A paused sequence still accepts enrollments and simply stops advancing them, which is why one that was paused and forgotten looks healthy from the outside while delivering nothing. It spends from the SEND budget rather than WRITE because activation lets the worker resume every waiting enrollment at once.


---

Rate limits: 100/min per key, counted against the organization's SEND ceiling (200/min). Both windows are one minute; there is no hourly or daily quota.