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

# Start an investigation

> Queues a Kapso Agent Investigator run for the finding. The investigation is
asynchronous; poll the finding to read the result.

Returns `422` when the finding already has an active investigation, is not
currently eligible for one, or the investigator is not configured for the project,
and `409` when another dispatch is in flight.




## OpenAPI

````yaml /api/platform/v1/openapi-platform.yaml post /findings/{finding_id}/start_investigation
openapi: 3.1.0
info:
  title: Kapso Platform API
  version: 0.2.0
  description: >
    Build WhatsApp messaging into your product. Manage customers, connect phone
    numbers, send broadcasts, and handle conversations.
servers:
  - url: https://api.kapso.ai/platform/v1
    description: Production
security:
  - ApiKeyAuth: []
tags:
  - name: Customers
    description: Manage customer accounts
  - name: Setup Links
    description: WhatsApp onboarding via embedded signup
  - name: Phone Numbers
    description: Connect and manage WhatsApp numbers
  - name: Webhooks
    description: Subscribe to WhatsApp events
  - name: Display Names
    description: Update WhatsApp business display names
  - name: Broadcasts
    description: |
      Send template messages at scale

      **Alpha**: This API is in alpha and subject to change
  - name: Conversations
    description: Manage conversation state
  - name: Media
    description: Upload media files for WhatsApp messaging
  - name: Users
    description: Manage project team members
  - name: Inbox Embeds
    description: Create and manage embeddable inbox access links
  - name: Webhook Deliveries
    description: View webhook delivery attempts and their status
  - name: External API Logs
    description: View logs of external API calls made by the project
  - name: Log Search
    description: Search log events across API, Meta, workflow, and webhook sources
  - name: Events
    description: Emit and query project-scoped events
  - name: Provider Models
    description: List available AI provider models
  - name: WhatsApp Flows
    description: Build interactive WhatsApp Flows for surveys and forms
  - name: Contacts
    description: Manage WhatsApp contacts
  - name: Findings
    description: Detect recurring problems in conversations and investigate them with AI
paths:
  /findings/{finding_id}/start_investigation:
    post:
      tags:
        - Findings
      summary: Start an investigation
      description: >
        Queues a Kapso Agent Investigator run for the finding. The investigation
        is

        asynchronous; poll the finding to read the result.


        Returns `422` when the finding already has an active investigation, is
        not

        currently eligible for one, or the investigator is not configured for
        the project,

        and `409` when another dispatch is in flight.
      operationId: startFindingInvestigation
      parameters:
        - name: finding_id
          in: path
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '202':
          description: Investigation queued
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FindingInvestigationAcceptedResponse'
              example:
                data:
                  finding_id: 8f14e45f-ceea-467a-9e1a-1b2c3d4e5f60
                  investigation_id: 1a2b3c4d-5e6f-4a7b-8c9d-0e1f2a3b4c5d
                  status: queued
        '401':
          $ref: '#/components/responses/UnauthorizedError'
        '404':
          description: >
            Finding not found (`finding_not_found`), or Findings is not enabled
            for this

            project (`findings_not_enabled`). Read `code` to tell them apart.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FindingsErrorResponse'
              example:
                error: Finding not found in this project.
                code: finding_not_found
        '409':
          description: An investigation dispatch is already in progress
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FindingsErrorResponse'
        '422':
          description: >-
            Finding is not eligible for investigation, or the investigator is
            not configured
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/FindingsErrorResponse'
              example:
                error: >-
                  The Finding is already being investigated or is not currently
                  eligible.
                code: investigation_unavailable
components:
  schemas:
    FindingInvestigationAcceptedResponse:
      type: object
      required:
        - data
      properties:
        data:
          type: object
          required:
            - finding_id
            - investigation_id
            - status
          properties:
            finding_id:
              type: string
              format: uuid
            investigation_id:
              type: string
              format: uuid
            status:
              type: string
              enum:
                - queued
                - investigating
                - completed
                - failed
                - timed_out
    FindingsErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: string
        code:
          type: string
          enum:
            - findings_not_enabled
            - finding_not_found
            - investigation_unavailable
          description: >
            Machine-readable reason. Present on both `404` cases and on an
            ineligible

            investigation. Absent on validation and pagination errors.
    ErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: string
  responses:
    UnauthorizedError:
      description: Missing or invalid API key
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key

````