Conversations

Change conversation status

Changes the lifecycle status of the conversation. The path id selects the conversation; the JSON body carries the new status (for example open, resolved, pending, or snoozed). When snoozing, include snoozed_until as an epoch timestamp indicating when the conversation should automatically reopen. Returns a boolean indicating success; the new status is reflected in the conversation's status (and snoozed_until) fields.

POST

https://api.nabrah.ai/api/ext/omni_v2/conversation/conversation/{id}/toggle_status

curl --request POST \
  --url 'https://api.nabrah.ai/api/ext/omni_v2/conversation/conversation/<id>/toggle_status' \
  --header 'X-API-Key: <your-api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "status": "resolved",
  "snoozed_until": 0
}'

false

Body fields

Set the target status and, for snoozing, the wake time.

status

Target lifecycle status: open, resolved, pending, or snoozed.

status

snoozed_until

Epoch timestamp at which a snoozed conversation should automatically return to open. Required when status is snoozed; set to 0 (or omit) for non-snooze transitions.

snoozed_until

Authorization

X-API-Keystringheaderrequired

Your workspace API key. Create one in the dashboard under API keys.

Path parameters

idintegerrequired

Integer id of the conversation whose status to change.

From a list endpoint or GET.../conversation/{id}.

Body

application/json

Mark the conversation as resolved.

Resolve

{
  "status": "resolved",
  "snoozed_until": 0
}

Response

200

Successful Response

application/json

422

Validation Error

application/json