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, review confirm_input_schema and the target tool event, then use task.confirmAction. 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). A non-empty message.connectors replaces the task's connector selection; omitting it or passing an empty array keeps the task's current selection. To clear the selection, use the top-level clear_connectors field.
Agent profile override for this turn and subsequent turns. Use the stable values standard, lite, or max, or a Max thinking level: max-medium, max-high, max-extra, or max-ultra. The thinking level also applies to subsequent turns; plain max keeps the level the task already uses; a task that has never selected a level uses the default, currently equivalent to max-extra. Versioned aliases such as 1.6-lite, 2.0-max, 2.0-max-ultra, 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 and thinking level; 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, max-medium, max-high, max-extra, max-ultra JSON Schema for structured output extraction, armed for the next time this task finishes (stop_reason: finish).
- A new schema replaces any previous one.
- Omitted — the current schema state is unchanged; an armed schema is not cleared.
See the Structured Output guide.
Clears the task's connector selection for this and subsequent turns. Cannot be combined with a non-empty message.connectors. Other task features may still provide tools. See the Connectors guide.