---
title: "Get a conversation"
method: GET
path: "/ai/conversations/{conversation_id}"
tags: ["Conversations"]
---

# Get a conversation

`GET /ai/conversations/{conversation_id}`

Retrieve a specific AI conversation by its ID.

## Path parameters

- `conversation_id` string, required

## Response `200`

Successful Response

- 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-2.md) · [All operations](https://skmtc.net/team-telnyx/apis/telnyx-api-2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/team-telnyx/telnyx-api-2/revisions/8f5f4e537994/schema)