# Conversation Object

This page is generated from the Collector OpenAPI source and defines the public `conversation` payload shape.

## Data dictionary

| Field                                | Type                    | Required | Description                                                                                        |
| ------------------------------------ | ----------------------- | -------- | -------------------------------------------------------------------------------------------------- |
| `content`                            | object                  | Yes      | Standard `conversation` content envelope used by the Collector and downstream presence processing. |
| `content.contentType`                | string                  | Yes      | Must be `conversation` for this shape.                                                             |
| `content.contentData`                | ConversationContentData | Yes      | Event-specific payload for a conversation turn.                                                    |
| `content.contentData.userId`         | string                  | Yes      | User identity for the conversation turn.                                                           |
| `content.contentData.agentId`        | string                  | Yes      | Agent or use case identity for the turn.                                                           |
| `content.contentData.conversationId` | string                  | Yes      | Conversation or thread identifier.                                                                 |
| `content.contentData.userMessageId`  | string                  | No       | Optional source-system ID for the user message.                                                    |
| `content.contentData.agentMessageId` | string                  | No       | Optional source-system ID for the assistant message.                                               |
| `content.contentData.userMessage`    | string                  | Yes      | Current user message text.                                                                         |
| `content.contentData.agentMessage`   | string                  | Yes      | Current assistant response text.                                                                   |
| `content.contentData.spaceId`        | string                  | No       | Optional space, channel, or grouping identifier.                                                   |

## Sample shape

```json
{
  "contentType": "conversation",
  "contentData": {
    "userId": "user_12345",
    "agentId": "agent_sales_assistant",
    "conversationId": "conv_a1b2c3",
    "userMessageId": "msg_user_001",
    "agentMessageId": "msg_agent_001",
    "userMessage": "Can you keep recommendations short and practical?",
    "agentMessage": "Absolutely. I will keep responses short and practical.",
    "spaceId": "default"
  }
}
```

## Downstream expectations

Conversation events use this shape when the collector feeds Presence intent classification and related conversation processing.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://tagit.gitbook.io/tagit/reference/reference/api/collector/conversation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.