We recommend you migrate any usage of
/chat/send-message and /chat/send-message-simple-api to this new API by
February 1st, 2026./chat/send-chat-message API is used to send a message to Onyx.
It is the same API that the Onyx frontend uses to send and receive messages.
You have the option of receiving a streaming response or the complete response as a string.
This guide was explain all of the parameters you can pass in to the API and provide a code sample.
Request Parameters
| Parameter | Description |
|---|---|
message | The user message to send to the Agent. |
llm_override | Pass an object to override the default LLM settings for this request. If None, you will get the default Onyx behavior. You can pass or exclude any of the following fields: • model_provider • model_version • temperature If you pass an invalid configuration (e.g., specifying claude-sonnet-4.5 when the default model_provider is OpenAI), your request will fail. |
allowed_tool_ids | Agents are created with a set of Actions they are allowed to invoke. You can further configure this set for your immediate interaction using this parameter. See the list of Actions and their IDs via the GET /tool endpoint. Pass in an empty list to disable all Actions. Pass in None to allow all the Actions which are configured for the Agent. |
forced_tool_id | Force the Agent to use a specific Action for this request. The Agent may run other Actions before returning its final response, but it will be guaranteed to use this one. Leave empty to let the Agent decide which Actions to use. |
file_descriptors | A list of files to include along with your request. File IDs can be found via the POST /user/projects/file/upload and the GET /user/projects/file/ endpoints. |
search_filters | Filters to narrow down the internal search results used by the Agent. All filter arguments are optional and can be combined: • source_type – Source types like web, slack, google_drive, confluence • document_set – The name of the document sets to search within • time_cutoff – ISO 8601 format: YYYY-MM-DDTHH:MM:SSZ • tags – Format: {"tag_key": "tag_value"} |
deep_research | Enables Deep Research mode for this request. Note: This mode consumes significantly more tokens, so be careful accessing it via the API. |
parent_message_id | The ID of the parent message in the chat history (primary-key for the previous message in the chat history tree). If not passed in, your new message is assumed to be sequentially after the last message. Warning: If set to None, the chat history is reset and the new message is considered the first message in the chat history. |
chat_session_id | To continue an existing conversation, pass in the chat session ID where the message should be sent. If left blank, a new chat session will be created according to chat_session_info. |
chat_session_info | Details about the chat session which will be used for all messages in the session. Fields can be left blank to use defaults. • persona_id – The ID of the Agent to use for the chat session • project_id – ID of a Project if the chat should be scoped to a Project |
stream | If true, responds with an SSE stream of individual packets (same set used for the Onyx UI). Fields like the Answer, reasoning tokens, and iterative Tool Calls need to be pieced together from streamed tokens. |
include_citations | If true, responses will include citations for the sources used to generate the answer. |