Append a message to a thread
Changed onAppend a user message to an existing thread and trigger a deferred run. When the thread already has a run in flight the message is queued, not refused: the response reports queued with the run ID the message's own run will start under after the earlier run ends. Queued messages run one at a time in the order they were appended. With wait, the server waits for the message's own run and never returns the earlier run's result.
Request
- Base URL: https://api.sazabi.com/v1
- URL: https://api.sazabi.com/v1/threads/{threadId}/messages
- Auth: none declared
Path parameters
Thread ID to append the message to.
Request body
Response
OK
Changes
- warning
added the new
queuedenum value to theresponse property for the response status
- warning
- warning
removed the request property
- warning
added the new
billing_account_missingenum value to the/response property for the response status - warning
added the new
billing_admission_unavailableenum value to the/response property for the response status - warning
added the new
credit_balance_depletedenum value to the/response property for the response status - warning
added the new
credit_balance_missingenum value to the/response property for the response status - warning
added the new
subscription_blockedenum value to the/response property for the response status - warning
added the new
subscription_missingenum value to the/response property for the response status
- warning