Add a comment

curl --fail-with-body --silent --show-error \ "https://api.getkato.io/v1/raycast/comments" \ -H "Authorization: Bearer $KATO_RAYCAST_ACCESS_TOKEN" \ -H "Content-Type: application/json" \ --data '{ "entityType": "task", "entityId": "task_example", "comment": "Brief is ready for review." }'

Add an activity comment to a task, record, or native meeting. Use an OAuth access token issued to kato-raycast. Developer keys cannot call this endpoint. See Raycast authentication. Required scopes: comments:write. Tasks must be visible, records must be active in the workspace, and meetings require full detail access. Unavailable targets return 404. A retry can add another comment; there is no comment idempotency token.

Parameters

string

required

task, record, or meeting.

string

required

Target ID, 1–200 characters.

string

required

Trimmed comment text, 1–10,000 characters.

Response

201 — Returns the resource under data. Example IDs and values are illustrative.

{
  "data": {
    "activityId": "activity_example"
  }
}

curl --fail-with-body --silent --show-error \
  "https://api.getkato.io/v1/raycast/comments" \
  -H "Authorization: Bearer $KATO_RAYCAST_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  --data '{
  "entityType": "task",
  "entityId": "task_example",
  "comment": "Brief is ready for review."
}'

This request changes workspace data. A timeout does not prove that the write failed; inspect the result before retrying.

API Reference

Developer identity

Objects and records

Tasks

Webhooks

CLI API

Raycast API

Raycast identity and discovery

Raycast tasks

Raycast records

Raycast meetings and activity

Raycast notifications

OAuth

Add a comment

Parameters

Response

​Parameters

​Response

Parameters

Response