Skip to main content
POST
Requires the owning active claim; releases takeover and appends a resolution event. A subsequent customer question can resume AI. Requires WIDGET_LIVE_CHAT_ENABLED=true, an admin bearer key and verified thread ownership. Responses use Cache-Control: no-store. Mutations share the customer/AI thread execution lease. Limited to 120 requests/minute per credential (shared with Redis when configured).

Path parameters

string
required
Native conversation ID

Request body

No request body.

Response

object
LiveChatSummary

Status codes

Using this contract

Read the source OpenAPI document for declared schemas and alternatives. This page also includes documented corrections from the spec overlays. Example IDs and values are illustrative; replace them with records from your workspace.
Last modified on November 13, 2026