---
title: "Move a contact to a sequence"
method: POST
path: "/v3/contacts/{id}/move-to-sequence"
tags: ["Contacts"]
---

# Move a contact to a sequence

`POST /v3/contacts/{id}/move-to-sequence`

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

Moves a contact to a different sequence, optionally removing from existing sequences

## Path parameters

- `id` integer, required

## Request body

- object
  - `sequenceId` integer, required — Target sequence ID to move the contact to
  - `removeFromExisting` boolean — Whether to remove the contact from their current sequence
  - `startStepId` integer, nullable — Optional step ID to start from in the target sequence
  - `ignoreStepDelay` boolean — If true, skip the configured delay before the first step and start processing immediately
  - `startFrom` string, date-time, nullable — Optional date when contact processing should begin. If not provided, processing starts immediately.

## Response `204`

Contact moved to sequence successfully. The response body is empty.

- unknown

## Other responses

- `400` — Validation failure on the route parameter or request body, or a business rule rejection (e.g. contact could not be added to the sequence).
- `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 contact
- `404` — Contact or sequence not found
- `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)