PUT
/v1/agent/conversations/{id}/assignee
Transfer Conversation (to an Agent)
The agent's half of a transfer, named and shaped exactly like the supervisor's route of the same path under /v1/admin, with one difference that matters: a supervisor may move any conversation, an agent may only hand on one they are **actually holding**. A former handler still sees the thread in their list and can read it, but a transfer from them is refused with 403. Records `reason: "transfer"` on the resulting lifecycle event, which is what lets the timeline tell an agent's handover from a supervisor's intervention. The former handler's unread counter is cleared with the handover, since nothing on it is waiting on them any more.
curl -X PUT https://api.{cluster}.{platform}.voiger.io/v1/agent/conversations/{id}/assignee \ -H "Cookie: sid=$VOIGER_SESSION" \ -H "x-workspace-code: your-workspace-code" \ -H "x-csrf-token: $CSRF_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "user_id": "6feb3aa5-e6d0-4931-aadd-5edd828bdb95" }'
Parameters
x-workspace-code
string
required
in header
x-csrf-token
string
required
in header
id
string
required
in path
Response
conversation