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

# conversation.item.created

Reports a new conversation item created by the client or by response generation.

## Event fields

<ResponseField name="event_id" type="string" required>
  Unique id for this server event.
</ResponseField>

<ResponseField name="type" type="string" required>
  Event type. Must be `conversation.item.created`.
</ResponseField>

<ResponseField name="previous_item_id" type="string | null" required>
  Conversation item that precedes this item. Returns `null` when the item has no predecessor.
</ResponseField>

<ResponseField name="item" type="object" required>
  The created Conversation Item. Uses the same item shape documented in `conversation.item.create`.
</ResponseField>

<ResponseField name="id" type="string" required>
  Server-assigned or client-provided conversation item identifier.
</ResponseField>

<ResponseField name="type" type="string" required>
  Item type, such as `message`, `function_call`, or `function_call_output`.
</ResponseField>

**role, content, `call_id`, name, arguments, output: conditional fields**

Fields depend on the item `type`. See the `item` schema in `conversation.item.create`.

<ResponseField name="status" type="string">
  Optional item status, when returned by the service.
</ResponseField>

<ResponseExample>
  ```json conversation.item.created theme={null}
  {
    "event_id": "evt_item_created_001",
    "type": "conversation.item.created",
    "previous_item_id": null,
    "item": {
      "id": "item_001",
      "type": "message",
      "status": "completed",
      "role": "user",
      "content": [
        {
          "type": "input_text",
          "text": "Show me the second product."
        }
      ]
    }
  }
  ```
</ResponseExample>