pub struct RealtimeConversationItem {
pub arguments: Option<String>,
pub call_id: Option<String>,
pub content: Option<Vec<RealtimeConversationItemContent>>,
pub id: Option<String>,
pub name: Option<String>,
pub object: Option<String>,
pub output: Option<String>,
pub role: Option<String>,
pub status: Option<String>,
pub _type: Option<String>,
}Fields§
§arguments: Option<String>The arguments of the function call (for function_call items).
call_id: Option<String>The ID of the function call (for function_call and function_call_output items). If passed on a function_call_output item, the server will check that a function_call item with the same ID exists in the conversation history.
content: Option<Vec<RealtimeConversationItemContent>>The content of the message, applicable for message items. - Message items of role system support only input_text content - Message items of role user support input_text and input_audio content - Message items of role assistant support text content.
id: Option<String>The unique ID of the item, this can be generated by the client to help manage server-side context, but is not required because the server will generate one if not provided.
name: Option<String>The name of the function being called (for function_call items).
object: Option<String>Identifier for the API object being returned - always realtime.item.
output: Option<String>The output of the function call (for function_call_output items).
role: Option<String>The role of the message sender (user, assistant, system), only applicable for message items.
status: Option<String>The status of the item (completed, incomplete). These have no effect on the conversation, but are accepted for consistency with the conversation.item.created event.
_type: Option<String>The type of the item (message, function_call, function_call_output).