Skip to main content
POST
Update Conversation Status

Authorizations

Authorization
string
header
required

Your API key (ta_live_…) from Settings → API keys, sent as Authorization: Bearer <key>. Keep it on a server: it can message every customer you have. A key is full, build or read-only; a request its level does not allow is refused with 403.

Headers

Thinnest-Workspace
string

Developers only: the customer workspace this request acts in — its org_… id from POST /customers. Leave it out to act in your own workspace.

Example:

"org_3fKq9TzQ1mN8vB2xR7cLpA"

Path Parameters

id
string
required

The conversation's id (conv_…).

Body

application/json
status
enum<string>
required

resolved: mark it done (fires conversation.resolved). active: hand it back to the agent. human_handling: take it over — the agent stays quiet until it is handed back.

Available options:
resolved,
active,
human_handling

Response

The conversation's state now, and whether this request changed it.

status
enum<string>
required

The state you asked for, which it is now in.

Available options:
resolved,
active,
human_handling
changed
boolean
required

False when it was already in that state: nothing was written or announced.