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

# Resolve a conversation handoff

> Requires `conversations:handoffs:write`. Resolves human ownership and returns the conversation to AI mode. Does not acknowledge an independent pending reply obligation.



## OpenAPI

````yaml /openapi.json post /conversations/{conversationId}/handoff/resolve
openapi: 3.0.3
info:
  title: Visito M2M API
  version: 1.0.0
  description: >-
    Tenant-scoped server-to-server API for channels, conversations, commerce,
    custom AI tools, and WhatsApp templates. Send operations are asynchronous
    and return queued acknowledgements. Expansion adds conversation controls,
    knowledge, sales opportunities, delivery status, reporting, and signed
    webhooks.
servers:
  - url: https://platform-api.visitoai.com/m2m/v1
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Channels
  - name: Conversations
  - name: Commerce
  - name: Custom tools
  - name: WhatsApp templates
  - name: Properties
  - name: Knowledge
  - name: Sales CRM
  - name: Delivery
  - name: Reporting
  - name: Webhooks
paths:
  /conversations/{conversationId}/handoff/resolve:
    post:
      tags:
        - Conversations
      summary: Resolve a conversation handoff
      description: >-
        Requires `conversations:handoffs:write`. Resolves human ownership and
        returns the conversation to AI mode. Does not acknowledge an independent
        pending reply obligation.
      operationId: m2mPostConversationsConversationidHandoffResolve
      parameters:
        - name: conversationId
          in: path
          required: true
          schema:
            type: string
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/HandoffResolveInput'
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HandoffResolution'
        default:
          $ref: '#/components/responses/Error'
components:
  schemas:
    HandoffResolveInput:
      type: object
      properties:
        resolutionNote:
          type: string
    HandoffResolution:
      type: object
      properties:
        ok:
          type: boolean
        conversationId:
          type: string
        handoffCaseId:
          type: string
        statusAfter:
          type: string
        manualEnabledAfter:
          type: boolean
        resolvedAt:
          type: string
          format: date-time
    ErrorResponse:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              example: M2M_AUTH_INSUFFICIENT_SCOPE
            message:
              type: string
            details:
              type: object
              additionalProperties: true
      example:
        error:
          code: M2M_AUTH_INSUFFICIENT_SCOPE
          message: M2M credential does not have required scope.
          details:
            requiredScopes:
              - conversations:write
            missingScopes:
              - conversations:write
  responses:
    Error:
      description: Structured error
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: Visito M2M API key
      description: Server-side tenant-scoped credential created from Build > API Keys.

````