Skip to main content
POST
Add a comment or reply
Write access: a member/administrator with a write-enabled credential, or an authorized signed-in user. Add a Markdown comment or a nested reply using parentId. Top-level comments have depth zero; replies support at most three nested levels. Mention with @email, @[Name](user:UUID), or mentionIds. Reuse the Idempotency-Key header on retries. Body is nonempty and at most 10,000 characters. Supports @email, user:UUID links and mentionIds. Root depth is zero; a fourth reply level returns 400 COMMENT_DEPTH_LIMIT. Comments advance board activity but do not produce activity-table rows. MCP clients can use add_comment for this operation. Request conventions · API keys · MCP connections

Authorizations

Authorization
string
header
required

Personal or team Mill REST API key

Headers

Origin
string<uri>

The exact configured Mill UI origin. Required for browser mutations carrying session cookies.

Idempotency-Key
string

Reuse the same key and exact request bytes for retries of one logical mutation; different content conflicts.

Required string length: 8 - 128
Pattern: ^[A-Za-z0-9._:-]+$

Path Parameters

taskId
string<uuid>
required

The taskId from the corresponding list, record or authorization response.

Body

application/json
body
string
required
Required string length: 1 - 10000
parentId
string<uuid>
Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$
mentionIds
string<uuid>[]
Maximum array length: 50
Pattern: ^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$

Response

Successful response. Examples are illustrative; field values vary by record.

Illustrative response shape. Fields can be absent in alternate successful flows; see the operation description and example.

comment
object