---
title: "Move contacts to a contact list"
method: POST
path: "/v3/contact-lists/{id}/move-contacts"
tags: ["Contact Lists"]
---

# Move contacts to a contact list

`POST /v3/contact-lists/{id}/move-contacts`

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

Moves contacts to the specified contact list. This is a non-atomic operation:
successfully moved contacts are not rolled back if some fail.
The response contains only the failed items with their error details.

## Path parameters

- `id` integer, required

## Request body

- object
  - `contactIds` integer[], required — Array of contact IDs to move

## Response `200`

Move operation completed. Response is a dictionary keyed by contact ID.
Only failed items appear; missing IDs were moved successfully.

Possible per-item error codes:

| error | Meaning |
|-------|---------|
| 8 | `ContactNotProcessed` — contact could not be moved (e.g. access denied, invalid ID) |

- object

## Other responses

- `400` — Route parameter / 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 does not have access to this list
- `404` — Contact list 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)