> ## Documentation Index
> Fetch the complete documentation index at: https://api.livechatai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get resolution analytics

> Post-close judgement of whether conversations actually solved the customer's problem, broken down by verdict (RESOLVED / UNRESOLVED) and by who carried the conversation (AI / HUMAN_AGENT / NONE).

Conversations are bucketed by their **creation date**, not their close or analysis date, matching the other analytics endpoints. Only conversations that are currently closed and have been analysed are counted; a conversation that was reopened leaves the metric until it is closed again.

Requires the resolution analysis add-on. Without it every count is 0.



## OpenAPI

````yaml get /api/v2/analytics/resolutions
openapi: 3.0.1
info:
  title: LiveChatAI API v2
  description: >-
    LiveChatAI API v2 - Build powerful AI-powered customer support experiences.
    This API follows REST principles with predictable, resource-oriented URLs,
    JSON responses, and standard HTTP methods.
  version: 2.0.0
servers:
  - url: https://app.livechatai.com
    description: Production server
security:
  - bearerAuth: []
paths:
  /api/v2/analytics/resolutions:
    get:
      tags:
        - Analytics
      summary: Get resolution analytics
      description: >-
        Post-close judgement of whether conversations actually solved the
        customer's problem, broken down by verdict (RESOLVED / UNRESOLVED) and
        by who carried the conversation (AI / HUMAN_AGENT / NONE).


        Conversations are bucketed by their **creation date**, not their close
        or analysis date, matching the other analytics endpoints. Only
        conversations that are currently closed and have been analysed are
        counted; a conversation that was reopened leaves the metric until it is
        closed again.


        Requires the resolution analysis add-on. Without it every count is 0.
      parameters:
        - in: query
          name: agentId
          required: true
          schema:
            type: string
            example: clx1234567890abcdef
          description: The ID of the agent/chatbot
        - in: query
          name: startDate
          required: true
          schema:
            type: string
            format: date
            example: '2024-01-01'
          description: >-
            Start of the range. `YYYY-MM-DD` is the start of that day in
            `timezone`; an ISO 8601 date-time with offset is used as-is.
        - in: query
          name: endDate
          required: true
          schema:
            type: string
            format: date
            example: '2024-01-31'
          description: >-
            End of the range, inclusive. `YYYY-MM-DD` covers the whole day in
            `timezone` (through 23:59:59.999); an ISO 8601 date-time with offset
            is used as-is.
        - in: query
          name: timezone
          schema:
            type: string
            example: America/New_York
          description: Timezone for date calculations (defaults to system timezone)
      responses:
        '200':
          description: Successfully retrieved resolution analytics data
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    example: success
                  data:
                    type: object
                    properties:
                      breakdown:
                        type: array
                        description: >-
                          One row per (verdict, handledBy) combination that
                          occurred in the range
                        items:
                          type: object
                          properties:
                            verdict:
                              type: string
                              enum:
                                - RESOLVED
                                - UNRESOLVED
                              example: UNRESOLVED
                            handledBy:
                              type: string
                              enum:
                                - AI
                                - HUMAN_AGENT
                                - NONE
                              example: HUMAN_AGENT
                            count:
                              type: number
                              example: 12
                      analyzedConversations:
                        type: number
                        example: 120
                        description: Total analysed conversations in the range
                      resolvedConversations:
                        type: number
                        example: 94
                        description: Conversations whose verdict is RESOLVED
                      unresolvedConversations:
                        type: number
                        example: 26
                        description: Conversations whose verdict is UNRESOLVED
                      resolutionRate:
                        type: number
                        example: 78
                        description: >-
                          Percentage of analysed conversations that ended
                          RESOLVED, rounded to a whole number
                      escalatedUnresolvedConversations:
                        type: number
                        example: 9
                        description: >-
                          Conversations escalated to a human agent that still
                          ended UNRESOLVED - the gap this metric exists to
                          surface
        '400':
          description: >-
            Bad request - missing agentId/startDate/endDate, or an unparseable
            date
        '401':
          description: Unauthorized - invalid or missing API token
        '404':
          description: Chatbot not found or access denied
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````