> ## 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.

# Get a chat result

> Read one chat session your organization owns, with its stored transcript.



## OpenAPI

````yaml /openapi/backend.json get /api/chats/sessions/{chat_id}
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/{chat_id}:
    get:
      tags:
        - Results
      summary: Get a chat result
      description: >-
        Read one chat session your organization owns, with its stored
        transcript.
      operationId: getChatResult
      parameters:
        - name: chat_id
          in: path
          required: true
          description: ID of a chat session your organization owns.
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: The chat session.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ChatResultResponse'
              example:
                err: false
                msg: Success
                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'
        '400':
          description: The chat session was not found in your organization.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorEnvelope'
              example:
                err: true
                msg: Chat session not found
        '403':
          $ref: '#/components/responses/Refused'
components:
  schemas:
    ChatResultResponse:
      type: object
      required:
        - err
        - msg
        - results
      properties:
        err:
          type: boolean
          example: false
        msg:
          type: string
          example: Success
        results:
          $ref: '#/components/schemas/ChatSession'
    ErrorEnvelope:
      type: object
      required:
        - err
        - msg
      properties:
        err:
          type: boolean
          example: true
        msg:
          type: string
          description: What went wrong.
    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.