task.sendMessage
Sends a follow-up message to a task for multi-turn conversation. Use this after task.create to continue talking, or to answer messageAskUser / cascadeAskUser questions with ordinary message.content. For supported action confirmations, use task.confirmAction, regardless of whether confirm_input_schema is present. Do not automatically confirm unrecognized waiting types.
Headers
API key for direct authentication. Provide either this or Authorization, not both. See Authentication.
Body
The unique identifier of the task to send the message to. Supports the shortcut agent-default-main_task for the IM agent's main task.
The follow-up message. Supports the same content formats as task.create (plain text or multi-part with files). Note: message.connectors behaves differently here than in task.create — a non-empty list overrides the task's connectors, while omitting it (or passing an empty array) reuses the connectors configured at task.create time rather than re-resolving project/user defaults. To remove all connectors, use the top-level clear_connectors field instead.
Agent profile override for this turn and subsequent turns. Use the stable values standard, lite, or max. Versioned aliases such as 1.6-lite, 2.0-max, and the legacy manus-1.6-lite form are also accepted; the version segment is ignored because model versions are not selected independently. A version without a suffix, such as 1.6 or manus-1.6, means standard. Omit the field (or pass an empty string) to keep the task's current profile; unlike task.create, this endpoint does not default to standard. Free personal accounts are downgraded to lite when an override is provided.
standard, lite, max JSON Schema for structured output extraction. Arms the schema for the next time this task finishes (stop_reason: finish). Sending a new schema replaces any previous one. Omitting this field leaves the current schema state unchanged — it does not clear an armed schema. See the Structured Output guide.
Removes all connectors from this task for this and subsequent turns. Combine with message.connectors to form three states: a non-empty message.connectors overrides the task's connectors with the new list; clear_connectors: true clears all connectors; omitting both reuses the connectors configured at task.create time. Passing a non-empty message.connectors together with clear_connectors: true is a conflict and returns InvalidArgument.