Skip to main content
POST
/
v1
/
escalations
/
{id}
/
resolve
Resolve escalation
curl --request POST \
  --url https://api.conduit.ai/v1/escalations/{id}/resolve \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{}'
{
  "data": {
    "id": "k578dfetqv2xv0b7bt9c6m4j5s7n8p1r",
    "workspace_id": "j57demo8f8x7c9v0n2q4r6t8y1u3i5o",
    "type": "chat",
    "conversation_id": "ph77c0dy0mgdpzmqz6tesry8w184002s",
    "contact_id": "ph77c0dy0mgdpzmqz6tesry8w184002s",
    "agent_run_id": "ar77c0dy0mgdpzmqz6tesry8w184002s",
    "agent_id": "ag77c0dy0mgdpzmqz6tesry8w184002s",
    "disposition": "escalated",
    "disposition_reason": "Early check-in availability requires property team confirmation.",
    "status": "pending",
    "created_at": "2026-04-03T05:42:10.000Z",
    "reviewed_at": null,
    "reviewed_by": null,
    "guest_message": "Can I check in before 3 PM tomorrow?",
    "proposed_response": "I can help confirm that for you. Let me check with the property team.",
    "request_for_additional_info": "Please confirm whether early check-in is available for this reservation.",
    "questions_for_operator": "Please confirm whether early check-in is available for this reservation."
  }
}

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
​
status
enum<string>

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

Available options:
reviewed,
resolved,
dismissed

Response

Resolved escalation

​
data
object
required

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

Example:
{
  "id": "k578dfetqv2xv0b7bt9c6m4j5s7n8p1r",
  "workspace_id": "j57demo8f8x7c9v0n2q4r6t8y1u3i5o",
  "type": "chat",
  "conversation_id": "ph77c0dy0mgdpzmqz6tesry8w184002s",
  "contact_id": "ph77c0dy0mgdpzmqz6tesry8w184002s",
  "agent_run_id": "ar77c0dy0mgdpzmqz6tesry8w184002s",
  "agent_id": "ag77c0dy0mgdpzmqz6tesry8w184002s",
  "disposition": "escalated",
  "disposition_reason": "Early check-in availability requires property team confirmation.",
  "status": "pending",
  "created_at": "2026-04-03T05:42:10.000Z",
  "reviewed_at": null,
  "reviewed_by": null,
  "guest_message": "Can I check in before 3 PM tomorrow?",
  "proposed_response": "I can help confirm that for you. Let me check with the property team.",
  "request_for_additional_info": "Please confirm whether early check-in is available for this reservation.",
  "questions_for_operator": "Please confirm whether early check-in is available for this reservation."
}