Admin/Set Conversation Status
PUT /v1/admin/conversations/{id}/status

Set Conversation Status

Force-resolve the conversation (supervisor action), optionally with tags and a wrap-up note.

Base URL https://api.{cluster}.{platform}.voiger.io
Request · cURL
curl -X PUT https://api.{cluster}.{platform}.voiger.io/v1/admin/conversations/{id}/status \
  -H "Cookie: sid=$VOIGER_SESSION" \
  -H "x-workspace-code: your-workspace-code" \
  -H "x-csrf-token: $CSRF_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "status": "resolved",
       "tags": [
         "billing"
       ],
       "note": "Customer confirmed delivery date."
     }'

Parameters

x-workspace-code string required in header
x-csrf-token string required in header
id string required in path

Response

conversation▾
object
id
string
status
string
state
string
tags▾
array The conversation's own tags. The full current set: the resolve dialog opens pre-filled from it, resolving by hand replaces it, and a wrap-up resolution adds to it. The client resolves names and colours for `tag_id` against its replicated tag store.
tag_id
string
actor
any
created_at
string
channels▾
object Every medium this conversation has used, as a map keyed by channel -- not just the one its latest activity rode. Maintained as the activities are written, so a client can filter and badge a thread without reading its timeline. A map rather than a list because each value is a channel's own object, empty today and room for detail later. Empty for a thread that has only routing events.
voice
object
whatsapp
object
sms
object
participants▾
array
id
string
type
string
reference_id
string
role
string | null
assigned_at
string | null
left_at
string | null
latest_activity
any
created_at
string
updated_at
string