---
title: "Add Channel Comment"
method: POST
path: "/inbox/channels/{channel_id}/comments"
tags: ["AI Inbox"]
---

# Add Channel Comment

`POST /inbox/channels/{channel_id}/comments`

## Request

- Base URL: `https://be.graph8.com/api/v1`
- URL: `https://be.graph8.com/api/v1/inbox/channels/{channel_id}/comments`
- Auth: HTTP bearer

Leave an INTERNAL note. Not a reply - the customer never sees it.

MENTIONING SOMEONE CREATES THEM A TASK in the Work app. The two mention
lists are additive rather than alternatives: an id with no matching email
still gets the task, it just gets no notification, so send both to get the
bell as well.

Attachments must already be uploaded; only their token and key are
load-bearing, because the server re-validates and never trusts a
client-sent name, size or type.

## Path parameters

- `channel_id` string, required: Conversation id.

## Query parameters

- `channel_type` 'email' | 'chat' | 'phone' | 'sms' | 'heyreach' | 'meetings' | 'support' | 'all', required: Which channel the conversation lives in. REQUIRED: the same id means different rows in different channels, so this is what identifies the conversation, not a filter.

## Headers

- `Authorization` string, nullable
- `X-Target-Org-Id` string, nullable

## Request body

- CommentCreateRequest: An INTERNAL note on a conversation. The customer never sees it. Mentioning someone creates them a task in the Work app. The two mention lists are ADDITIVE rather than alternatives: an id with no matching email still gets the task, it just gets no notification - so sending both is how you get the bell as well.
  - `content` string, required
  - `attachments` CommentAttachmentRef[]
    - `token` string, required
    - `key` string, required
    - `name` string, nullable
    - `size` integer, nullable
    - `type` string, nullable
  - `mentioned_user_ids` string[]: Mentioned users by id. Each gets a Work task.
  - `mentioned_user_emails` string[]: The same users by email. Additive - this is what drives the notification.

## Response `201`

Successful Response

- ApiResponseInboxPayload
  - `data` InboxPayload, required: An open envelope for a comment, an assignment or a workspace. Open because a comment carries attachment refs and mention metadata that grow, and because an assignment result reports per-assignee outcomes.
  - `pagination` PaginationMeta
    - `page` integer, required: Current page number (1-indexed)
    - `limit` integer, required: Items per page
    - `total` integer, required: Total number of items
    - `has_next` boolean, required: Whether there are more pages
    - `next_cursor` string, nullable: Opaque cursor for the next page; null when there are no more items. Pass it back as the `cursor` query param to fetch the following page without computing page numbers.
    - `total_available` integer, nullable: Search endpoints only: how many records really match, when known. Can be larger than `total`, which is capped at the 10,000 results that can be paged. For company search this is a distinct-company estimate. Null when unknown; absent outside search.
    - `total_is_lower_bound` boolean, nullable: Search endpoints only: true when more records match than `total` shows (the result set is larger than the 10,000 results that can be paged). Absent outside search.
    - `notes` string[], nullable: Search endpoints only: plain-language notes about the result, e.g. that more records match than can be paged, or that a reversed `between` range was put in order.

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/graph8/apis/graph8-developer-api.md) · [All operations](https://skmtc.dev/graph8/apis/graph8-developer-api/llms.txt) · [OpenAPI document](https://skmtc.dev/graph8/apis/graph8-developer-api/revisions/2e7cfa0ca921?raw)