Send a message
Queue a user-authored message through the same durable SYM-node and Gateway flow used by SYM-OS. Hermes slash commands are preserved exactly; send /new to request a reset of this exact chat's current Hermes conversation.
API 2.7.0 · Published service contract ↗
Request
Base URL: https://app.sym.so/v1/workspaces/{workspace_id}
Authentication: bearer. Required scope: messages:send.
POST /agents/{agent_id}/chats/{chat_id}/messages
Queue a user-authored message through the same durable SYM-node and Gateway flow used by SYM-OS. Hermes slash commands are preserved exactly; send /new to request a reset of this exact chat's current Hermes conversation.
| Parameter | Type | Description |
|---|---|---|
agent_idpath · required | string | Required agent_id path identifier. |
chat_idpath · required | string | Accessible chat ID. |
Idempotency-Keyheader · required | string | Client-generated key that prevents duplicate work. |
response_contextbody | object | Optional per-message presentation metadata: {"channel":"voice","verbosity":"concise"}. Requests a brief conversational reply without reducing task completeness or changing profile instructions. Omit for ordinary text turns. Requires a worker supporting this contract; keep the original content unchanged. |
curl --fail-with-body -X POST "https://app.sym.so/v1/workspaces/$WORKSPACE_ID/agents/$AGENT_ID/chats/$CHAT_ID/messages" \
-H "Authorization: Bearer $SYM_WORKSPACE_API_KEY" \
-H "Content-Type: application/json" \
--data "{\"content\":\"/new\",\"client_message_id\":\"reset-chat-unique-001\"}"{
"worker_id": "worker-example-001",
"org_id": "workspace_example",
"message": {
"id": "msg_01JA",
"status": "queued"
},
"chat": {
"id": "chat_01J8",
"status": "responding"
},
"ok": true
}Authorization
{
"type": "bearer",
"scope": "messages:send",
"transport": "Authorization: Bearer <workspace_api_key>"
}Errors
| Status | Description |
|---|---|
| 400 | The request body or parameters are invalid. |
| 401 | The workspace API key is missing, invalid, expired, or revoked. |
| 403 | The key lacks the required scope or its owner no longer has permission. |
| 404 | The resource is missing or intentionally hidden by authorization. |
| 429 | The key exceeded its current rate limit. |
Usage notes
- A successful response proves durable queueing and dispatch, not that an unhealthy runtime consumed or acknowledged /new.
- WorkspaceAPI currently exposes no first-class session rebind, chat-runtime restart, profile Gateway restart, tmux kill, or force-new-runtime operation.