Skip to main content
Endpoint · POST /conversation/actions
Two actions change the conversation’s state (inbox_status): mark_resolved marks it as resolved and mark_pending as pending. Neither carries fields.

mark_resolved

Marks the conversation as resolved.
If the thread has untranscribed audio, mark_resolved can fail with TRANSCRIPTION_REQUIRED_TO_RESOLVE (integrity guard). It does not escalate to a human: fix it and retry.

mark_pending

Marks the conversation as pending.
In a list, these objects go in the actions array of a POST /conversation/actions — see Assembling an action list.

Executable example

The mark_resolved and mark_pending actions on a conversation identified by phone and channel. Neither carries fields: they only change the inbox_status.

Request

Response

202 Accepted — the group was accepted and runs in the background. The per-action result does not travel in the response (query it later — see How it runs).
string
Always processing: confirms the group was accepted and is running.
integer
How many actions in the array were admitted for execution — not how many succeeded.