Skip to main content
POST
Resolve escalation

Authorizations

Authorization
string
header
required

Conduit API token. Use Authorization: Bearer <token>. Read/write endpoints require a token with write access.

Path Parameters

id
string
required

Escalation id.

Example:

"k578dfetqv2xv0b7bt9c6m4j5s7n8p1r"

Query Parameters

workspace_id
string

Optional workspace override. If omitted, Conduit resolves the escalation's workspace automatically.

Example:

"j57demo8f8x7c9v0n2q4r6t8y1u3i5o"

Body

application/json

Request body for resolving a chat escalation. The status defaults to resolved when omitted.

status
enum<string>

Terminal status to move the escalation into. Defaults to resolved.

Available options:
reviewed,
resolved,
dismissed

Response

Resolved escalation

Single chat escalation response.

data
object
required

Single chat escalation entry with review status, assignee, and escalation context when available.

Example: