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

# Get a conversation by ID

> Retrieves detailed information about a specific conversation by its unique identifier.




## OpenAPI

````yaml GET /v1/fetch-conversation/{conversation_id}
openapi: 3.0.3
info:
  title: SalesCaptain API Documentation Service
  description: >
    API Documentation Service for SalesCaptain platform.

    This service provides endpoints for managing and retrieving company
    information for API documentation purposes.
  version: 0.1.0
  contact:
    name: SalesCaptain API Team
    email: support@salescaptain.com
  license:
    name: Proprietary
    url: https://salescaptain.com/license
servers:
  - url: https://api.salescaptain.com
    description: Production server
security:
  - BearerAuth: []
tags:
  - name: Health
    description: Service health and status endpoints
  - name: Companies
    description: Company management and retrieval operations
  - name: Accounts
    description: Account management and retrieval operations
  - name: Conversation Profiles
    description: Conversation profile management for communication channels
  - name: Conversations
    description: Conversation management and retrieval operations
  - name: Contacts
    description: Contact management and retrieval operations
  - name: Custom Fields
    description: Custom field definition management
externalDocs:
  description: SalesCaptain API Documentation
  url: https://docs.salescaptain.com
paths:
  /v1/fetch-conversation/{conversation_id}:
    get:
      tags:
        - Conversations
      summary: Fetch a single conversation by ID
      description: >
        Retrieves detailed information about a specific conversation by its
        unique identifier.
      operationId: fetchConversation
      parameters:
        - name: conversation_id
          in: path
          required: true
          description: Unique identifier for the conversation
          schema:
            type: string
            format: uuid
            example: b2c3d4e5-f6a7-8901-bcde-f12345678901
      responses:
        '200':
          description: Conversation fetched successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    example: Conversation fetched successfully!
                  conversation:
                    type: object
                    properties:
                      data:
                        $ref: '#/components/schemas/Conversation'
              example:
                message: Conversation fetched successfully!
                conversation:
                  data:
                    contact_id: a1b2c3d4-e5f6-7890-abcd-ef1234567890
                    contact_name: John Doe
                    contact_number: '+1234567890'
                    contact_email: john.doe@example.com
                    conversation_id: b2c3d4e5-f6a7-8901-bcde-f12345678901
                    conversation_profile_id: c3d4e5f6-a7b8-9012-cdef-123456789012
                    conversation_profile_number: '+1987654321'
                    conversation_profile_email: support@company.com
                    last_message: Hey, I need help with my order
                    assigned_to: d4e5f6a7-b8c9-0123-def1-234567890123
                    updated_at: '2026-03-17T10:30:00.000Z'
                    created_at: '2026-03-15T08:00:00.000Z'
                    seen_by: e5f6a7b8-c9d0-1234-ef12-345678901234
                    is_chat_opened: true
        '400':
          description: Missing required parameters
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                status: failure
                error: 'Required parameters missing: conversation_id'
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '403':
          $ref: '#/components/responses/ForbiddenError'
        '404':
          description: Conversation not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                status: failure
                error: Problem encountered while fetching conversation!
        '429':
          $ref: '#/components/responses/RateLimitError'
        '500':
          $ref: '#/components/responses/InternalServerError'
      security:
        - BearerAuth: []
components:
  schemas:
    Conversation:
      type: object
      description: Conversation information object
      properties:
        contact_id:
          type: string
          format: uuid
          description: Unique identifier for the contact
          example: a1b2c3d4-e5f6-7890-abcd-ef1234567890
        contact_name:
          type: string
          description: Contact's full name
          example: John Doe
        contact_number:
          type: string
          nullable: true
          description: Contact's phone number
          example: '+1234567890'
        contact_email:
          type: string
          format: email
          nullable: true
          description: Contact's email address
          example: john.doe@example.com
        conversation_id:
          type: string
          format: uuid
          description: Unique identifier for the conversation
          example: b2c3d4e5-f6a7-8901-bcde-f12345678901
        conversation_profile_id:
          type: string
          format: uuid
          description: Unique identifier for the conversation profile
          example: c3d4e5f6-a7b8-9012-cdef-123456789012
        conversation_profile_number:
          type: string
          nullable: true
          description: Phone number of the conversation profile
          example: '+1987654321'
        conversation_profile_email:
          type: string
          format: email
          nullable: true
          description: Email address of the conversation profile
          example: support@company.com
        last_message:
          type: string
          nullable: true
          description: Content of the last message in the conversation
          example: Hey, I need help with my order
        assigned_to:
          type: string
          format: uuid
          nullable: true
          description: Account ID of the assigned agent (null if unassigned)
          example: d4e5f6a7-b8c9-0123-def1-234567890123
        updated_at:
          type: string
          format: date-time
          description: Timestamp when the conversation was last updated
          example: '2026-03-17T10:30:00.000Z'
        created_at:
          type: string
          format: date-time
          description: Timestamp when the conversation was created
          example: '2026-03-15T08:00:00.000Z'
        seen_by:
          type: string
          format: uuid
          nullable: true
          description: >-
            Account ID of the last agent who viewed the conversation (null if
            unseen)
          example: e5f6a7b8-c9d0-1234-ef12-345678901234
        is_chat_opened:
          type: boolean
          description: Whether the chat is currently open
          example: true
      required:
        - contact_id
        - contact_name
        - conversation_id
        - conversation_profile_id
        - updated_at
        - created_at
        - is_chat_opened
    Error:
      type: object
      description: Error response object
      properties:
        error:
          type: string
          description: Error message
          example: Invalid request parameters
        code:
          type: string
          description: Error code for programmatic handling
          example: INVALID_PARAMS
        timestamp:
          type: string
          format: date-time
          description: Timestamp when the error occurred
          example: '2023-12-01T10:30:00Z'
        path:
          type: string
          description: API endpoint path where the error occurred
          example: /v1/fetch-companies
      required:
        - error
  responses:
    UnauthorizedError:
      description: Authentication token is missing or invalid
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Unauthorized access
            code: UNAUTHORIZED
            timestamp: '2023-12-01T10:30:00Z'
            path: /v1/fetch-companies
    ForbiddenError:
      description: Access forbidden - valid token but insufficient permissions
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Forbidden access
            code: FORBIDDEN
            timestamp: '2023-12-01T10:30:00Z'
            path: /v1/fetch-companies
    RateLimitError:
      description: Rate limit exceeded
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Too many requests, please try again later
            code: RATE_LIMIT_EXCEEDED
            timestamp: '2023-12-01T10:30:00Z'
            path: /v1/fetch-companies
      headers:
        X-RateLimit-Limit:
          description: Request limit per time window
          schema:
            type: integer
            example: 30
        X-RateLimit-Remaining:
          description: Remaining requests in current window
          schema:
            type: integer
            example: 0
        X-RateLimit-Reset:
          description: Time when the rate limit resets
          schema:
            type: integer
            example: 1701425400
    InternalServerError:
      description: Internal server error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Problem encountered while fetching companies!
            code: INTERNAL_ERROR
            timestamp: '2023-12-01T10:30:00Z'
            path: /v1/fetch-companies
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >
        Authentication token required for accessing protected endpoints.

        The token should be obtained from the main SalesCaptain authentication
        service.

````