Comment on a task
The tasks.comments.create operation: POST /api/v1/tasks/{id}/comments in the REST API and the tasks_comments_create tool in the MCP server.
/api/v1/tasks/{id}/commentsAdds a comment to a task's thread: a question, progress, or why something is blocked. Anyone who may work on the entity's tasks can comment, also on finished tasks and while someone else holds the task. Comments can't be edited or deleted. Never put credentials (portal passwords, PINs, certificates) in a comment.
At a glance
- REST:
POST /api/v1/tasks/{id}/comments - MCP tool:
tasks_comments_create - Operation ID:
tasks.comments.create - Scope: Organization, or one of its legal entities or brands
- Permission:
tasks:write - Risk tier:
write - Dry run: Supported (send
Ownrecord-Dry-Run: true) - Idempotency:
Idempotency-Keyrequired - Modes: Test and live
- Authentication: API key with the
tasks:writescope - Since: M10
Request
Path parameters
| Field | Type | Description |
|---|---|---|
id | task_… ID |
Body
A JSON object (Content-Type: application/json):
| Field | Type | Required | Description |
|---|---|---|---|
body | string | Yes |
Response
201 Created with a JSON object:
| Field | Type | Description |
|---|---|---|
id | tcm_… ID | |
object | "task_comment" | |
taskId | task_… ID | |
author | object | |
author.type | string | |
author.id | string | |
body | string | |
createdAt | date-time |
Examples
Report progress
POST /api/v1/tasks/task_01m4ttwd3veh9apbewxheq5xa9/comments
Authorization: Bearer or_test_…
Idempotency-Key: 3f1c9a52-7d0e-4b8f-9a61-0c2d5e8b7f14
Content-Type: application/json
{
"body": "The portal asks for a second confirmation code; waiting for the finance team."
}
Response (201):
{
"id": "tcm_01m4ttwd3veh9apbewxheq5xa4",
"object": "task_comment",
"taskId": "task_01m4ttwd3veh9apbewxheq5xa9",
"author": {
"type": "agent",
"id": "agt_01m4ttwd3veh9apbewxheq5xa6"
},
"body": "The portal asks for a second confirmation code; waiting for the finance team.",
"createdAt": "2026-10-15T09:20:00.000Z"
}
Errors
| Code | HTTP status | When | What to do |
|---|---|---|---|
validation_failed | 400 | The comment is empty or too long. | Fix the fields listed in details.issues and send the request again. |
resource_not_found | 404 | No task with this ID in this organization, entity and mode. | Check the ID and that your credentials are scoped to the right organization, entity, brand and mode. |
permission_denied | 403 | You can't work on compliance tasks here. | Ask an organization owner or admin for a role or scope that allows this action. |
It can also return these common errors: api_version_unsupported, invalid_json, unsupported_media_type, authentication_required, api_key_invalid, idempotency_key_required, idempotency_key_reused, idempotency_in_progress, approval_required, approval_rejected, approval_expired, stale_approval, approval_policy_denied, rate_limited, internal_error.