Disable AI

Disables AI responses for a conversation. Once disabled, the assistant will stop generating replies — any new messages in the conversation will be stored but not answered by the AI.

This is useful for human takeover flows: configure a mid-call tool or automation that calls this endpoint when a customer requests to speak with a human agent.

Authentication

This endpoint requires your API key as a Bearer token.

Path Parameters

Response Fields

Error Responses

curl -X POST "https://app.voxlink.ai/api/user/conversations/7c9e6679-7425-40de-944b-e07fc1f90ae7/disable-ai" \
  -H "Authorization: Bearer YOUR_API_KEY"

const conversationId = '7c9e6679-7425-40de-944b-e07fc1f90ae7';

const response = await fetch(
  `https://app.voxlink.ai/api/user/conversations/${conversationId}/disable-ai`,
  {
    method: 'POST',
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY',
    },
  }
);

const data = await response.json();
console.log(data.ai_enabled); // false

import requests

conversation_id = '7c9e6679-7425-40de-944b-e07fc1f90ae7'

response = requests.post(
    f'https://app.voxlink.ai/api/user/conversations/{conversation_id}/disable-ai',
    headers={'Authorization': 'Bearer YOUR_API_KEY'}
)

data = response.json()
print(data['ai_enabled'])  # False

{
  "status": true,
  "ai_enabled": false
}

{
  "status": false,
  "error": "Conversation not found"
}

{
  "error": "Unauthorized"
}

Human Takeover Flow

A common pattern is to configure a mid-call tool that triggers this endpoint when the customer asks to speak with a human:

1. Create a mid-call tool (e.g. transfer_to_human) with a webhook pointing to your ActivePieces or automation flow
2. In your automation flow, call POST /user/conversations/{uuid}/disable-ai using your API key
3. Notify your support team (e.g. via Slack, email, or CRM) with the conversation UUID
4. The AI stops responding — your agent takes over by sending messages directly

To re-enable AI later, use the Enable AI endpoint.