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

# Get agent queue status

> Get information about agent availability and expected waiting times for customer service



## OpenAPI

````yaml https://dev.enneo.dev/api/mind/docs/open-api get /agents/queue
openapi: 3.0.0
info:
  version: '1'
  title: enneo.MIND API
  description: This describes the API of enneo Mind, the main ticketing backend
  contact:
    name: enneo GmbH
    email: richard@enneo.ai
  license:
    name: Proprietary software
    url: https://enneo.ai
servers:
  - url: https://demo.enneo.ai/api/mind
    description: Production server, demo client
  - url: https://main.enneo.dev/api/mind
    description: Development main branch
  - url: http://localhost:8005/api/mind
    description: Local development server
security:
  - bearerAuth:
      - api
  - cookieAuth:
      - api
paths:
  /agents/queue:
    get:
      tags:
        - General
      summary: Get agent queue status
      description: >-
        Get information about agent availability and expected waiting times for
        customer service
      operationId: getAgentsQueue
      responses:
        '200':
          description: Successful operation
          content:
            application/json:
              schema:
                type: object
                properties:
                  agentQueue:
                    type: number
                    description: >-
                      Number of waiting conversations per available suitable
                      agent. If this is for example 2.5, we have 2.5 chats that
                      first need to be handled per agent until there is capacity
                      for a new request. If -1, then there are no agents
                      available
                  liveConversationPossible:
                    type: object
                    description: >-
                      Indicates if a realtime conversation is possible per
                      channel
                    properties:
                      chat:
                        type: boolean
                        description: >-
                          Whether chat requests can be handled in realtime by a
                          human agent
                  expectedWaitingTime:
                    type: object
                    description: >-
                      Estimated waiting times per channel in seconds. If -1,
                      there are no humans available, and any incoming chat will
                      be handled offline.
                    properties:
                      chat:
                        type: number
                        description: >-
                          Estimated waiting time for chat channel before it is
                          handled by a human. If -1, responses are done via
                          email.
                  success:
                    type: boolean
              examples:
                noAgentsAvailable:
                  value:
                    agentQueue: -1
                    liveConversationPossible:
                      chat: false
                    expectedWaitingTime:
                      chat: -1
                    success: true
                  summary: No agents available
                agentsWithQueue:
                  value:
                    agentQueue: 2.5
                    liveConversationPossible:
                      chat: true
                    expectedWaitingTime:
                      chat: 145
                    success: true
                  summary: Agents available with waiting queue
        '403':
          description: Unauthorized
        '500':
          description: Internal error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      description: Data format of Enneo error messages
      properties:
        error:
          type: string
          example: Contract 121 could not be processed
          description: Readable error message that should be shown to the user
        details:
          type: string
          example: >-
            Uncatched null point exception in testFunction() in
            /app/src/file:212
          description: Not easily readable error message that is for the developer
        txId:
          type: string
          example: c916167c94
          description: >-
            Internal transaction id. Useful for debugging. Corresponds to the
            OpenTelemetry trace ID.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: JWT-based authentication
      x-scopes:
        api: Full access to the API
    cookieAuth:
      type: apiKey
      in: cookie
      name: connect.sid
      description: Cookie-based authentication
      x-scopes:
        api: Full access to the API

````