---
title: "Change Outbound Seat"
method: POST
path: "/gtm-internal/outbound/change-seat"
tags: ["gtm-internal"]
---

# Change Outbound Seat

`POST /gtm-internal/outbound/change-seat`

## Request

- Base URL: `https://api-v1.unusual.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://api-v1.unusual.ai/gtm-internal/outbound/change-seat`
- Auth: OAuth 2
  - Password
  - Token URL: `/auth/login`

Switch WHO this thread's email sends as — any current unusual.ai
admin — then rewrite the live draft so it reads naturally as the new
sender (a takeover, not an identity fiction). Two cases share the door:
correcting a mis-derived seat, and a real handover (Sarah picking up
Will's thread). On a handover the ORIGINAL seat is stamped once in
channel_refs and stays CC'd on every email send after; the campaign
alias is never CC'd.

Allowed wherever the pending message sends as an email: campaign-email
threads, and LinkedIn threads whose draft is a direct email. A pure
LinkedIn reply's sender is structural (the conversation belongs to one
seat's account).

## Request body

- ChangeSeatRequest
  - `thread_id` string, required
  - `seat` string, required

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/unusual/apis/dashboard-server.md) - [All operations](https://skmtc.dev/unusual/apis/dashboard-server/llms.txt) - [OpenAPI document](https://skmtc.dev/unusual/apis/dashboard-server/revisions/89f716930ead?raw)