Create Message
Body
The text contents of the message.
The role of the entity that is creating the message. Allowed values include:
user: Indicates the message is sent by an actual user and should be used in most cases to represent user-generated messages.assistant: Indicates the message is generated by the assistant. Use this value to insert messages from the assistant into the conversation.
user, assistant A list of files attached to the message, and the tools they should be added to.
Set of 16 key-value pairs that can be attached to an object. This can be useful for storing additional information about the object in a structured format. Keys can be a maximum of 64 characters long and values can be a maxium of 512 characters long.
Response
Represents a message within a thread.
If applicable, the ID of the assistant that authored this message.
A list of files attached to the message, and the tools they were added to.
The Unix timestamp (in seconds) for when the message was completed.
The content of the message in array of text and/or images.
The Unix timestamp (in seconds) for when the message was created.
The identifier, which can be referenced in API endpoints.
The Unix timestamp (in seconds) for when the message was marked as incomplete.
On an incomplete message, details about why the message is incomplete.
Set of 16 key-value pairs that can be attached to an object. This can be useful for storing additional information about the object in a structured format. Keys can be a maximum of 64 characters long and values can be a maxium of 512 characters long.
The object type, which is always thread.message.
thread.message The entity that produced the message. One of user or assistant.
user, assistant The ID of the run associated with the creation of this message. Value is null when messages are created manually using the create message or create thread endpoints.
The status of the message, which can be either in_progress, incomplete, or completed.
in_progress, incomplete, completed Was this page helpful?