---
title: "Bulk change sequence owner"
method: POST
path: "/v3/sequences/batch/owner"
tags: ["Sequences"]
---

# Bulk change sequence owner

`POST /v3/sequences/batch/owner`

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

Changes the owner of multiple sequences at once. Non-atomic — some may succeed while others fail.

## Request body

- object
  - `ids` integer[], required — List of sequence IDs to reassign
  - `userId` integer, required — Target user ID to assign as owner

## Response `200`

Dictionary of failed items keyed by sequence ID. Empty object `{}` means all succeeded.

Per-item failures use the `SequenceActionError` enum. Common per-item slugs:

| Slug | Meaning |
| --- | --- |
| `notFound` | Sequence does not exist |
| `forbidden` | Caller lacks permission for this sequence |
| `ownerLimitExceeded` | Target user has reached their sequence ownership limit |

- object

## Other responses

- `400` — Validation failure on the request body, or a business rule rejection (target user not a team member, owner limit exceeded).
- `401` — Unauthorized. The response body is empty; check the `WWW-Authenticate` header for the expected scheme.
- `403` — User lacks required feature scope to change sequence owners
- `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/versions/1c3d32eaf95e/schema)