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 Sigma.
It is the same API that the Sigma 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.
message
message
The user message to send to the Agent.
llm_override
llm_override
Pass an object to override the default LLM settings for this request. If
None,
you will get the default Sigma behavior.You can pass or exclude any of the following fields: model_provider, model_version, temperatureIf you pass an invalid configuration,
for example if the default model_provider is OpenAI and you only specify claude-sonnet-4.5,
your request will fail.allowed_tool_ids
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
forced_tool_id
Force the Agent to use a specific Action for this request. A specific tool/action which must be run by the Agent.
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
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
search_filters
Filters to narrow down the internal search results used by the Agent.
All filters arguments are optional and can be combined.
source_type: Source types likeweb,slack,google_drive,confluencedocument_set: The name of the document sets to search withintime_cutoff: Only include documents created or modified after this timestamp. ISO 8601 format:YYYY-MM-DDTHH:MM:SSZ(e.g.,2024-01-01T00:00:00Z).tags: Document tags in the format{"tag_key": "tag_value"}. Only documents with matching tags will be searched.
deep_research
deep_research
Enables Deep Research mode for this request.Note that this mode consumes significantly more tokens, so be careful accessing it via the API.
parent_message_id
parent_message_id
The ID of the parent message in the chat history. This is the primary-key (unique identifier)
for the previous message in the chat history tree.If not passed in, it is assumed that your new message is sequentially after the last message in the chat history.
chat_session_id
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 for the message according to
chat_session_info (see below).chat_session_info
chat_session_info
Details about the chat session which will be used for all messages in the session.
The field values can be left blank to use the default chat settings.
persona_id: The ID of the Agent to use for the chat sessionproject_id: ID of a Project if the chat should be scoped to a Project. Projects are used to organize files and instructions and are a lighter-weight version of Agents. Through programmatic use, it is typically recommended to use Agents instead.
stream
stream
If true, then it responds with an SSE stream of individual packets. This is the same set used for the Sigma UI.
Fields like the Answer, reasoning tokens, and iterative Tool Calls need to be pieced together from streamed tokens.
