tasks

Post Trail Message

Post a message on a task trail (protocol v0.2 trail_messages): kind question, answer, handoff or discussion. A message never completes a task, never satisfies a gate and never pages anyone. The actor is stamped from your credential (key:<id>, actor_type "key" — a credential, never a human), never from the body; the executor and the reviewer consume a key's answers only when the key holds agent:dispatch. On an ordinary task this is write tier. On a CYCLE task (one with coord) it needs agent:dispatch (agent:dispatch:code when the task, or the asker a question task stands for, is CODE:/SHELL:) because the text can become executor prompt or reviewer input. kind=answer on a dispatcher-addressed question task answers it through coord_answer_question and releases the blocked asker; a human-addressed question is answered only on the worker page (403 here). finding (reviewer runner) and decision (human completion) cannot be posted. Body ≤ 8000 chars; idempotency_key makes a replay return the same message.

post/tasks/{task_id}/messages

Request

  • Base URL: https://app.tascan.io/api/v1
  • URL: https://app.tascan.io/api/v1/tasks/{task_id}/messages
  • Auth: HTTP bearer

Path parameters

task_idstring required

Request body

kind'question' | 'answer' | 'handoff' | 'discussion' required

question = a question for the record (does not block anything); answer = answers a dispatcher question task and releases the asker; handoff = hand work or context to the next agent; discussion = a note.

bodystring required

The message text (1-8000 chars). Treated as DATA by every reader; on a cycle task it may be prepended to the executor prompt as TRAIL INPUT.

reply_tostring

Optional message id this replies to.

build_refstring

Optional sha256:<64 hex> the message is about (defaults to the cycle task's bound build).

addressee'human' | 'dispatcher'

Optional, kind=question only: who the question is for (recorded; nobody is paged).

idempotency_keystring

Optional replay key (≤ 200 chars): the same key on the same task returns the same message id.

Response

Success. JSON body: { data: ... } or an error object { error, message }.

Changes

No recorded changes to this operation across all 1 revision of this API.