Open or close a conversation
Moves a conversation between the two lifecycle states: Active (in the inbox, being worked) and Closed (finished).
When to use it. When the operator is done with a thread, or to reopen one closed too early. Reopening on a new customer message does not depend on this call — the contact writing again puts the conversation back in front of the operator either way.
What it is not. This is not the state chip in the conversation header (Open, Waiting on customer, Escalated, Resolved, …). Those are labels, set with PUT /conversations/{uuid}/label, and they describe where the work stands. Status only answers is this thread still open at all — a conversation can be Active and labelled Escalated at the same time.
Who can call it. A workspace API token, or a per-user JWT holding loop.conversations.status. A JWT only reaches conversations routed to one of its active queues; anything else answers 404 rather than 403, so a token cannot probe for conversations it may not see.
Authorizations
Use a Bearer token to access these API endpoints. Example: "Bearer {your-token}"
Path Parameters
Body
Active = open in the inbox; Closed = work finished
Active, Closed "Closed"