Conversations
Update Conversation Statuses
Open or close up to 100 conversations in one request
POST
Update Conversation Statuses
Open or close several conversations at once, for example every conversation on one page of List Conversations. Only conversations whose status changes are updated, so you can safely retry a request after a timeout: conversations that already have the status are reported as unchanged.
Closed conversations are reopened automatically when the subscriber replies or when you send a new outbound message.
Requests whose
Request
string[]
required
Conversation IDs to update, up to 100 distinct IDs. Surrounding whitespace is
trimmed, and blank or repeated IDs are ignored before the limit is checked. At
least one non-blank ID is required.
string
required
New status for every listed conversation:
open or closed.Response
boolean
true when the request was processed.string
The status that was applied:
open or closed.integer
Number of distinct conversation IDs in the request.
integer
Number of conversations whose status changed.
integer
Number of conversations that already had the status.
integer
Number of IDs that do not exist in your company. They are skipped; the rest of
the request still applies.
string[]
IDs whose status changed, in request order.
string[]
IDs that already had the status, in request order.
string[]
IDs that do not exist in your company, in request order.
conversationIds array has no usable IDs or more than 100 distinct IDs return 400. A missing or unknown status, or a missing or non-array conversationIds, returns 422. Rejected requests change no conversations. The API key needs the conversations:write scope.