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

# List chat sessions

> List chat sessions owned by your organization. Filters narrow the list within your organization; they cannot reach past it.



## OpenAPI

````yaml /openapi/backend.json get /api/chats/sessions
openapi: 3.0.3
info:
  title: Drive Health operational API
  version: 1.0.0
  description: >-
    Server-to-server API for organizations integrating with Drive Health. It
    starts chat and voice conversations and reads the calls, chats, transcripts,
    and recordings those conversations produce. Authenticate every request with
    an organization API key.
servers:
  - url: https://backend.drivehealth.ai
    description: Production. Use the API origin supplied for your environment.
security:
  - organizationBearer: []
  - organizationApiKey: []
tags:
  - name: Chat
    description: >-
      Start a chat with a caregiver, exchange messages, and end the session.
      These routes also answer on the compatibility mount `/v1/chat/...`.
  - name: Voice
    description: Start phone calls from an owned number and register browser voice calls.
  - name: Results
    description: >-
      Read the calls, chat sessions, transcripts, and recordings your
      organization owns.
paths:
  /api/chats/sessions:
    get:
      tags:
        - Results
      summary: List chat sessions
      description: >-
        List chat sessions owned by your organization. Filters narrow the list
        within your organization; they cannot reach past it.
      operationId: listChatSessions
      parameters:
        - $ref: '#/components/parameters/Page'
        - $ref: '#/components/parameters/Limit'
        - $ref: '#/components/parameters/AssistantFilter'
      responses:
        '200':
          description: A page of chat sessions.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ChatSessionListPage'
              example:
                count: 1
                next: null
                previous: null
                results:
                  - chat_id: 9f8e7d6c-5b4a-4938-8271-6a5b4c3d2e1f
                    assistant_id: 1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d
                    assistant_name: Appointments
                    status: active
                    user_message_count: 1
                    assistant_message_count: 2
                    created_at: '2026-10-20T14:02:11Z'
                    updated_at: '2026-10-20T14:03:05Z'
        '403':
          $ref: '#/components/responses/Refused'
components:
  parameters:
    Page:
      name: page
      in: query
      description: Page number, starting at 1.
      schema:
        type: integer
        minimum: 1
        default: 1
    Limit:
      name: limit
      in: query
      description: Number of records per page.
      schema:
        type: integer
        minimum: 1
        default: 10
    AssistantFilter:
      name: assistant_id
      in: query
      description: Return only records for this caregiver.
      schema:
        type: string
        format: uuid
  schemas:
    ChatSessionListPage:
      type: object
      required:
        - count
        - next
        - previous
        - results
      properties:
        count:
          type: integer
          minimum: 0
          description: Total number of matching chat sessions.
        next:
          type: string
          format: uri
          nullable: true
          description: Next page URL, or null.
        previous:
          type: string
          format: uri
          nullable: true
          description: Previous page URL, or null.
        results:
          type: array
          items:
            $ref: '#/components/schemas/ChatSession'
    ChatSession:
      type: object
      description: >-
        A chat session your organization owns. Records include further fields
        that this reference does not describe yet.
      additionalProperties: true
      properties:
        chat_id:
          type: string
          format: uuid
        assistant_id:
          type: string
          format: uuid
          description: The caregiver in the chat.
        assistant_name:
          type: string
        status:
          type: string
          description: Session status, for example `active`.
        user_message_count:
          type: integer
          minimum: 0
        assistant_message_count:
          type: integer
          minimum: 0
        transcript:
          type: string
          nullable: true
          description: The stored transcript as text.
        transcript_object:
          description: The stored transcript as structured turns, or null.
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
    Refusal:
      type: object
      required:
        - detail
      properties:
        detail:
          type: string
          description: Why the request was refused.
  responses:
    Refused:
      description: >-
        Refused before the endpoint ran, with `detail` instead of the standard
        envelope: the key is missing, invalid, or revoked; more than one
        credential was presented; or a selector names a different organization.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Refusal'
          examples:
            invalidKey:
              summary: Invalid or revoked key
              value:
                detail: Unauthorized
            noCredential:
              summary: No credential
              value:
                detail: Authentication credentials were not provided.
            conflictingCredentials:
              summary: More than one credential
              value:
                detail: >-
                  More than one credential was presented. Send an organization
                  key or a session token, not both.
            foreignSelector:
              summary: Selector names another organization
              value:
                detail: >-
                  This key belongs to a different organization than the request
                  selected.
  securitySchemes:
    organizationBearer:
      type: http
      scheme: bearer
      description: >-
        An organization API key starting with `dh_`, sent as `Authorization:
        Bearer dh_your_api_key`.
    organizationApiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Alternative to the Authorization header. Send one credential per
        request.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.