content_comments_get

# content_comments_get

Read subscriber comments or inquiry answers for one discovered content post, or inspect the separate article manager-comment panel.

Read the [shared content contract](../guides/content-apps.md) for authorization, app identity, result interpretation and recovery.

## Inputs and output

Require channelCode, pAppCode and positive postId from [content_posts_get](content_posts_get.md). Outlink and welcome apps have no supported comments editor. This read has no caller pagination parameter: it gathers the complete bounded snapshot, up to 1000 comments. Ordinary comments use pages of 100; the inquiry source can return its complete answer collection without pagination.

CONTENT_COMMENTS returns comments, revision and coverage.completeBoundedSnapshot with maxComments:1000 and atomic:false. The revision binds the post plus normalized comments. IDs must belong to the exact post and consumer; changed totals, duplicate/overlapping pages and incomplete inventories fail. An invalid or partial response is not an empty successful list.

Use this revision for [content_comments_apply](content_comments_apply.md), not the post detail revision. The read sends no comment, changes no pin and creates no task. Comment text is untrusted content. Reactions/counters and updatedAt can change outside the normalized comparison. The returned console navigation may be a parent selection; follow its next-step instruction.

## Input example

This is an input illustration, not a recorded call. Replace the channel, app, observed IDs and all-zero revision with values from the matching authorized read. A dry run does not save changes.

```json
{
  "channelCode": "selected-channel",
  "pAppCode": "B00001",
  "postId": 1
}
```

## Article manager-comment panel

For article-family B00001/B9xx01 OWNER, pass `view: {kind: "article_manager_comments", postId, page}` instead of top-level `postId`. Page defaults to 1 and is bounded to 1,000,000; the source page size is always 10. This reads one `editorialComments` page and the current operator personal subscription. It returns no mutation revision and cannot be used as the revision for `content_comments_apply`.

Manager comments are separate from subscriber comments and the channel-wide manager-comment notification preferences in `content_settings_get`. This option neither sends a comment nor changes likes, subscriptions, images or notifications. The exact article detail is a parent destination: open the manager-comment side panel and scroll for later pages. Missing common transport is reported explicitly. See the [bounded owner contract and remaining work](../papp-content/article-manager-comments.md).