Skip to main content
POST
SendMessage
Questions or issues? Contact us at api-support@manus.ai.
Auth:
  • API Key: Full access.
  • Standard OAuth client: Requires create_task or manage_all_tasks. With create_task, only tasks created by the same client; see Task visibility.
  • Trusted client: Full access.

Headers

x-manus-api-key
string

API key for direct authentication. Provide either this or Authorization, not both. See Authentication.

Authorization
string

OAuth2 access token in Bearer {token} format. An OAuth client requires the create_task or manage_all_tasks scope unless it is a Trusted team client or Trusted public client. Provide either this or x-manus-api-key, not both. See the Open App guide.

Example:

"Bearer {access_token}"

Body

application/json
task_id
string
required

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.

message
object
required

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

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.

Available options:
standard,
lite,
max
structured_output_schema
object

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.

clear_connectors
boolean
default:false

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.

Response

Message sent successfully. The task will resume processing.

ok
boolean

Whether the request was successful.

Example:

true

request_id
string

Unique identifier for this API request.

task_id
string

The ID of the task the message was sent to.