---
title: "Update a sequence"
method: PUT
path: "/v4/sequences/{id}"
tags: ["Sequences"]
---

# Update a sequence

`PUT /v4/sequences/{id}`

Updates any sequence settings — `name`, `email_address`, schedule (`send_days`, `send_hour`, `time_zone`), `email_template_id`, `exclude_subscriber_sources`, or the `active` / `repeat` / `hold` flags. Only fields included in the request body change; everything else is preserved.

Some changes have user-visible side effects on subscribers already in the sequence:

**Note:** flipping `active` from `false` to `true` resumes delivery for queued subscribers. Flipping it back to `false` pauses the sequence — subscribers stay in their current position but no new emails are sent until it's reactivated.

**Note:** changing the schedule (`send_days`, `send_hour`, or `time_zone`) only affects future sends. It does not retroactively reschedule emails already queued for delivery.

**Warning:** turning off `repeat` while subscribers are mid-sequence does not stop them from finishing — but they won't be re-eligible to start over after completing.

See [Create a sequence](/api-reference/sequences/create-a-sequence) for the full sequence model and what each field controls.

## Path parameters

- `id` integer, required

## Request body

- object
  - `name` string — The name of the sequence.
  - `email_address` string — The sending email address to use. Uses the account's sending email address if not provided.
  - `email_template_id` integer — Id of the email template to use.
  - `send_days` string[] — The days of the week to send the sequence on. Must be one of: `monday`, `tuesday`, `wednesday`, `thursday`, `friday`, `saturday`, `sunday`.
  - `send_hour` integer — The hour of the day to send the sequence at. Must be an integer between 0 and 23.
  - `time_zone` string — The timezone to use for the sequence. Must be a valid IANA timezone string.
  - `active` boolean — `true` to activate the sequence, `false` to deactivate it.
  - `repeat` boolean — When `true`, subscribers can restart the sequence multiple times.
  - `hold` boolean — When `true`, subscribers added via Visual Automations stay in the sequence after receiving the last email.
  - `exclude_subscriber_sources` object[] — The subscriber sources to exclude from the sequence.
    - `type` string, required — The type of subscriber source to exclude. Must be one of: `tag`, `sequence`, `form`, `segment`.
    - `ids` integer[], required

## Response `200`

Updates the sequence and returns its details

- object
  - `sequence` object, required
    - `id` integer, required
    - `name` string, required
    - `hold` boolean, required
    - `repeat` boolean, required
    - `created_at` string, required
    - `updated_at` string, required
    - `email_address` string, required
    - `email_template_id` integer, required
    - `send_days` string[], required
    - `send_hour` integer, required
    - `time_zone` string, required
    - `active` boolean, required
    - `exclude_subscriber_sources` object[], required
      - `type` string, required
      - `ids` integer[], required
    - `email_count` integer
    - `subscriber_count` integer

## Other responses

- `401` — Returns a 401 if the token and/or account cannot be authenticated
- `404` — Returns a 404 when the provided id does not exist
- `422` — Returns a 422 with an error message when one or more of the parameters were invalid

---

[API](https://skmtc.net/kit/apis/kit-api.md) · [All operations](https://skmtc.net/kit/apis/kit-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/kit/kit-api/versions/0df0c90d12da/schema)