Create task comment

POST/v1/tasks/{taskId}/comments

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
taskIdpathstringYesTask ID
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
bodystringNo
contentstringNoRaw text content.
authorTypeuser | agent | systemNo
authorAgentIdstringNo
authorNamestringNo
sourceThreadIdstringNo
threadIdstringNoThread ID.
metadataobjectNoFree-form metadata object.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

201Task comment createdapplication/json
FieldTypeRequiredDescription
commentobjectNo
comment.objectstringNo
comment.idstringNoUnique identifier.
comment.userIdstringNoUser ID.
comment.projectIdstringNoProject ID.
comment.taskIdstringNo
comment.taskobjectNo
comment.task.objectstringNo
comment.task.idstringNoUnique identifier.
comment.task.projectIdstringNoProject ID.
comment.task.releaseIdstringNo
comment.task.titlestringNoDisplay title.
comment.task.statusbacklog | todo | in_progress | blocked | doneNoCurrent lifecycle status.
comment.task.prioritylow | medium | high | urgentNo
comment.task.sprintIdstringNo
comment.task.assigneeAgentIdstringNo
comment.bodystringNo
comment.authorTypeuser | agent | systemNo
comment.authorAgentIdstringNo
comment.authorNamestringNo
comment.sourceThreadIdstringNo
comment.threadIdstringNoThread ID.
comment.metadataobjectNoFree-form metadata object.
comment.createdAtstringNoISO 8601 timestamp.
comment.updatedAtstringNoISO 8601 timestamp.
Create task comment
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow