---
title: "Update conversation metadata"
method: PUT
path: "/ai/conversations/{conversation_id}"
tags: ["Conversations"]
---

# Update conversation metadata

`PUT /ai/conversations/{conversation_id}`

Update metadata for a specific conversation.

## Path parameters

- `conversation_id` string, required

## Request body

- UpdateConversationRequest
  - `metadata` object — Metadata associated with the conversation. Set `ai_disabled` to `true` to stop AI from responding to messages (e.g., when a human agent takes over). Set to `false` to re-enable AI responses.

## Response `200`

Successful Update

- object
  - `data` Conversation
    - `id` string, uuid, required
    - `name` string
    - `created_at` string, date-time, required — The datetime the conversation was created.
    - `metadata` object, required — Metadata associated with the conversation. Telnyx provides several pieces of metadata, but customers can also add their own. The reserved field `ai_disabled` (boolean) can be set to `true` to prevent AI-generated responses on this conversation. When `ai_disabled` is `true`, calls to the chat endpoint will return a 400 error. Set to `false` or remove the field to re-enable AI responses. This is useful when a human agent needs to take over the conversation mid-stream (e.g., a technician stepping in while AI was messaging a resident).
    - `last_message_at` string, date-time, required — The datetime of the latest message in the conversation.

## Other responses

- `404` — Conversation Not Found
- `422` — Validation Error

---

[API](https://skmtc.net/team-telnyx/apis/telnyx-api.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api/versions/e32d46c5945b/schema)