> ## Documentation Index > Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt > Use this file to discover all available pages before exploring further. # List Escalations > Retrieve a paginated list of all escalations in your workspace. ## OpenAPI ````yaml GET /v1/escalations openapi: 3.0.0 info: title: Conduit API version: 1.0.0 description: Public API for Conduit. servers: - url: https://api.conduit.ai description: Production security: [] tags: - name: meta description: Discovery and API metadata endpoints. - name: agents description: >- V2 chat agent configuration, including instructions, skills, triggers, and automation behavior. - name: contacts description: >- Contact profile and contact-scoped related resources such as tickets and calls. - name: workspaces description: Workspaces accessible to the current API token. - name: escalations description: >- Chat escalations that require operator review, including message, proposed response, and disposition context when available. - name: conversations description: >- Canonical message threads. Use these endpoints to list threads, inspect conversation state, read transcripts, and send replies. - name: conversation-tags description: >- Conversation labels, root topics, and subtopics used for classification and topic analytics. - name: tickets description: >- Operational queue items tied to conversations, including ticket-scoped transcripts and replies. - name: calls description: Phone call records, transcripts, summaries, and recordings when available. - name: reservations description: >- PMS reservations synced from the workspace's integrations (Hostaway, Guesty, Airbnb, etc.), including guest identity, payment status, and stay dates. - name: appointments description: >- Scheduled appointments (bookings) backed by the Conduit booking service. Exposes allocation context and the upstream booking-service `external_id`. - name: helpdesk_tickets description: >- Helpdesk tickets mirrored from external helpdesk integrations (Zendesk, Pylon, Plain), including requester identity and upstream metadata. - name: kb description: >- Knowledge base search and node management. Nodes represent knowledge base entries (files or directories), chunks are the indexed retrieval units used by search. - name: skills description: >- Workspace agent skills that can be attached to V2 chat agents. Sidebar/global-assistant skills are intentionally excluded. - name: custom_tools description: >- Custom code tools: user-authored Python/JavaScript functions executed in a sandbox when an agent calls them. Includes a runtimes endpoint describing the entrypoint signature, return shape, and available dependencies per language. - name: inbox_types description: >- Workspace inbox types. Each id is stable and usable as a message trigger's `inboxTypeId` and as the `inbox_type_id` filter on list conversations. paths: /v1/escalations: get: tags: - escalations summary: List chat escalations description: >- Returns cursor-paginated chat escalations for a workspace. Each result includes the current status, guest message, proposed response, operator question, and disposition when available. operationId: listEscalations parameters: - schema: type: string description: Workspace to query. example: j57demo8f8x7c9v0n2q4r6t8y1u3i5o required: true name: workspace_id in: query - schema: type: integer minimum: 1 maximum: 100 required: false name: limit in: query - schema: type: string required: false name: cursor in: query - schema: type: string enum: - pending - reviewed - resolved - dismissed description: Optional escalation status filter. required: false name: status in: query responses: '200': description: Chat escalations content: application/json: schema: type: object properties: data: type: array items: type: object properties: id: type: string workspace_id: type: string type: type: string enum: - chat conversation_id: type: string nullable: true contact_id: type: string nullable: true agent_run_id: type: string nullable: true agent_id: type: string nullable: true disposition: type: string nullable: true enum: - escalated - escalation_and_answer - resolved - unresolved - no_op disposition_reason: type: string nullable: true status: type: string enum: - pending - reviewed - resolved - dismissed created_at: type: string reviewed_at: type: string nullable: true reviewed_by: type: object nullable: true properties: id: type: string name: type: string email: type: string picture_url: type: string nullable: true required: - id - name - email - picture_url assignee: type: object nullable: true properties: id: type: string name: type: string email: type: string picture_url: type: string nullable: true required: - id - name - email - picture_url guest_message: type: string nullable: true proposed_response: type: string nullable: true request_for_additional_info: type: string nullable: true questions_for_operator: type: string nullable: true required: - id - workspace_id - type - conversation_id - contact_id - agent_run_id - agent_id - disposition - disposition_reason - status - created_at - reviewed_at - reviewed_by - assignee - guest_message - proposed_response - request_for_additional_info - questions_for_operator description: >- Single chat escalation entry with review status, assignee, 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 assignee: 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. next_cursor: type: string nullable: true has_more: type: boolean required: - data - next_cursor - has_more description: >- Cursor-paginated chat escalations response with escalation context when available. example: 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 assignee: 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. next_cursor: page-token has_more: true '400': description: Invalid request content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '401': description: Unauthorized content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '403': description: Forbidden content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id '429': description: Rate limit exceeded content: application/json: schema: type: object properties: error: type: string required: - error description: Standard error response. example: error: Invalid workspace id security: - bearerAuth: [] components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: API Token description: >- Conduit API token. Use `Authorization: Bearer `. Read/write endpoints require a token with write access. ````