--- title: "List a post's comments" method: GET path: "/v1/{account_id}/posts/{post_id}/comments" tags: ["Posts"] --- # List a post's comments `GET /v1/{account_id}/posts/{post_id}/comments` ## Request - Base URL: `https://api.curviate.com` - URL: `https://api.curviate.com/v1/{account_id}/posts/{post_id}/comments` - Auth: HTTP bearer Returns top-level comments on a post (v2 drops the reply-fetch mode, use the Comments group's dedicated replies endpoint). Full comment text is included. ## Path parameters - `account_id` string, required - `post_id` string, required ## Query parameters - `limit` integer - `cursor` string - `sort_by` 'MOST_RECENT' | 'MOST_RELEVANT' ## Response `200` Top-level comments on the post (reply-mode is dropped in v2, see the Comments group for replies), plus the next-page cursor. Comment text is returned verbatim. - object - `object` 'comment_list': Response type discriminator. - `items` object[]: Page of top-level comments. - `object` 'comment': Response type discriminator. - `id` string: Comment identifier (bare numeric string). - `created_at` string, nullable: ISO-8601 UTC datetime the comment was created, or null. - `text` string, nullable: Full comment text (content pass-through, never stored). - `reply_count` number: Total reply count on this comment. - `reactions` object[]: Per-reaction-type count buckets. - `type` 'like' | 'celebrate' | 'support' | 'love' | 'insightful' | 'funny': Reaction type (unified lowercase enum). - `count` number: Count of this reaction type on the comment. - `reaction_count` number: Total reaction count on this comment, the sum of reactions[].count. - `author` object: Author of the comment. - `id` string: LinkedIn profile identifier. - `name` string: Author's display name. Absent on the shape that carries `display_name` instead. - `display_name` string: Author's display name. Absent on the shape that carries `name` instead. - `object` string: Author entity discriminator, on the shape that carries one. - `type` string: Author entity type (for example individual or organization), on the shape that carries one. - `can_reply` boolean: true if the authenticated account can reply to this comment. - `can_react` boolean: true if the authenticated account can react to this comment. - `is_sender` boolean: true if the authenticated account authored this comment. - `attachments` object[]: Attachment metadata (inline only). - `id` string: Attachment identifier. - `mimetype` string: Attachment MIME type. - `type` string: Attachment type (e.g. img, file). - `filename` string: Original filename, when known. - `file_size` number: File size in bytes, when known. - `cursor` string, nullable: Next-page cursor; null on the last page. cursor:null does not confirm completeness when limit is small, the underlying pagination is offset-based. - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite. - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture. - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail). - `hint` object, required - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy. - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text. - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each. - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload. ## Other responses - `400`: limit out of range (1-50), malformed cursor, invalid sort_by, or an unknown query param (comment_id is removed in v2). - `401`: Missing or invalid API key. - `404`: The account_id does not belong to this tenant (ACCOUNT_NOT_FOUND), or the post was not found (RESOURCE_NOT_FOUND). An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id. - `429`: Rate limited, slow down and retry after the hinted delay. - `500`: Internal error. - `502`: A temporary error occurred. Please try again. - `503`: Service unavailable. - `504`: Gateway timeout. --- [API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)