Completions
Tune Studio
- Assistants
- Model
- Finetuning
- Logs
- User
- Studio
- Thread Datasets
- POSTCreate thread dataset
- POSTList thread datasets
- POSTGet thread dataset
- POSTUpdate thread dataset
- POSTDelete a thread dataset
- POSTAdd threads to a dataset
- POSTRemove threads from a dataset
- POSTReplace thread messages
- POSTCreate and save a thread in a dataset
- POSTList threads in a dataset
- POSTList messages in threads in a dataset
- POSTExport a thread dataset
- POST
- Runs
- Run Steps
- Threads
- Messages
Replace thread messages
Replace messages in a thread dataset.
Tune API Keys are the preferred way to authenticate with the API. You can create an API Key from your Tune Studio Profile → 'Access Keys' (in sidebar)
The organization ID for request, it override the x-org-id header if set.
The ID of dataset.
The ID of thread to replace messages.
List of messages to replace (all old messages will be replaced with these messages).
Authorizations
Tune API Keys are the preferred way to authenticate with the API. You can create an API Key from your Tune Studio Profile → 'Access Keys' (in sidebar)
Body
The ID of dataset.
The ID of thread to replace messages.
List of messages to replace (all old messages will be replaced with these messages).
The ID of the message.
"thread.message".
The time the message was created.
The ID of the thread the message is associated with.
"user" or "assistant".
The content of the message.
"text" or "image_file".
only used if type is "text".
The attachments of the message.
The ID of the file.
The tool that created the file.
The name of the function.
The description of the function.
The parameters of the function in JSON format.
The required parameters of the function.
The action data of the function.
The ID of the run that created the message.
Metadata for the message key-value pairs.
Response
The ID of dataset.
The ID of thread.
List of messages replaced.
The ID of the message.
"thread.message".
The time the message was created.
The ID of the thread the message is associated with.
"user" or "assistant".
The content of the message.
"text" or "image_file".
only used if type is "text".
The attachments of the message.
The ID of the file.
The tool that created the file.
The name of the function.
The description of the function.
The parameters of the function in JSON format.
The required parameters of the function.
The action data of the function.
The ID of the run that created the message.
Metadata for the message key-value pairs.
Was this page helpful?