Send a follow-up message to a task
Tasks
Send task message
Append a user message to an existing task. Used when an agent is in
waiting_for_input (it called ask_user) or when continuing a conversational
task. The orchestrator queues a new_message event so the agent can resume.
The message is processed asynchronously — poll GET /v1/tasks/{task_id} to
observe the status change.
POST
Send a follow-up message to a task
Authorizations
Workspace API key issued from the web app. Pass as
Authorization: Bearer YOUR_API_KEY.
Path Parameters
UUID of the task.
Body
application/json
Text to deliver to the agent as a user message.
Response
Message accepted and queued for the agent.
ID of the newly created task message.
Lifecycle status of a task.
pending— created, not yet picked upqueued— held back by admission control (agent at concurrent-task limit)running— being processed by the workerwaiting_for_input— agent calledask_user; reply withPOST /tasks/{id}/messageawaiting_review— agent is paused for human approval of a sensitive stepcompleted— terminal: finished successfullyfailed— terminal: errored outstopped— terminal: cancelled by a user or system
Available options:
pending, queued, running, waiting_for_input, awaiting_review, completed, failed, stopped Human-readable acknowledgement.