A message that is rendered as one coherent unit with one given sender.
| Field | Type | Required | Description |
|---|---|---|---|
agent_config |
Optional[models.AgentConfig] | ➖ | Describes the agent that executes the request. |
author |
Optional[models.Author] | ➖ | N/A |
citations |
List[models.ChatMessageCitation] | ➖ | : warning: ** DEPRECATED **: Deprecated on 2026-02-06, removal scheduled for 2026-10-15: Use inline citations via ChatMessageFragment.citation and ChatMessageCitation.referenceRanges instead. This field is still populated for backward compatibility.. Deprecated: Use inline citations via ChatMessageFragment.citation instead. For detailed reference information, use ChatMessageCitation.referenceRanges. This field is still populated for backward compatibility. |
uploaded_file_ids |
List[str] | ➖ | IDs of files uploaded in the message that are referenced to generate the answer. |
fragments |
List[models.ChatMessageFragment] | ➖ | A list of rich data used to represent the response or formulate a request. These are linearly stitched together to support richer data formats beyond simple text. |
ts |
Optional[str] | ➖ | Response timestamp of the message. |
message_id |
Optional[str] | ➖ | A unique server-side generated ID used to identify a message, automatically populated for any USER authored messages. |
message_tracking_token |
Optional[str] | ➖ | Opaque tracking token generated server-side. |
message_type |
Optional[models.MessageType] | ➖ | Semantically groups content of a certain type. It can be used for purposes such as differential UI treatment. USER authored messages should be of type CONTENT and do not need messageType specified. |
has_more_fragments |
Optional[bool] | ➖ | : warning: ** DEPRECATED **: This will be removed in a future release, please migrate away from it as soon as possible. Signals there are additional response fragments incoming. |