Fetch Many Comments
Comment Endpoints
Fetch Many Comments
Get a paginated, sorted list of comments
GET
Fetch Many Comments
Returns a paginated list of comments. Used for both top-level comment threads (filter byDocumentation Index
Fetch the complete documentation index at: https://docs.replyke.com/llms.txt
Use this file to discover all available pages before exploring further.
entityId) and reply threads (filter by parentId). Also used for user profile comment history (filter by userId).
Deleted comments in thread view appear as stripped placeholders to preserve tree structure (Reddit-style). Authors viewing their own comments always see full data.
Query Parameters
Filter comments by entity. Returns all comments (top-level and replies) for this entity.
Filter to replies of a specific comment. Used to fetch a reply thread.
Filter to comments by a specific user. When this matches the authenticated user’s ID, soft-deleted comments are included with full data.
Filter by the
sourceId of the entity. Only effective when include contains entity.Sort order. One of:
new— newest firstold— oldest firsttop— by net upvotes (upvotes minus downvotes)controversial— high total votes with a close up/down split
Page number (1-indexed).
Number of comments per page. Maximum
100.Comma-separated list of associations to include. Valid values:
user, entity, space.Requesting
space automatically includes entity as well, since space membership is resolved via the entity.
Requesting user also includes the user’s avatar and banner file URLs.Response
Returns a paginated response:userId filter), removed comments appear as stripped placeholders: userId, user, content, gif, mentions, and attachments are nulled out. Structural fields such as id, parentId, entityId, reactionCounts, repliesCount, createdAt, updatedAt, metadata, and foreignId are retained so the tree can be rendered. This applies to both user-deleted comments (always stripped) and moderation-removed comments (stripped for non-authors; the author sees full data).
