> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sublay.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Fetch many comments
> Fetch one level of a comment thread, cursor-paginated, with optional nested replies
export const SpaceReputationParams = ({variant = "context", field = "path"}) => {
const isUser = variant === "user";
return <>
Opt-in. Adds a spaceReputation number to each returned user,
scoped to a single space. Requires the reputation bundle.
The reputation total is always present regardless;{" "}
spaceReputation is purely additive and only appears when you
pass this object. This object is the primary form — it
replaces the deprecated flat props below. See the{" "}
Reputation data model for the
full contract.
{isUser ?
Which bucket to read. A space <uuid> reads that
space's bucket; "none" reads the
project-general (space-less) bucket.{" "}
"context" is rejected (400) on this
endpoint — there is no space context to derive. The empty string
and the legacy general / null aliases are
also rejected. Missing buckets read as 0.
:
Which bucket to read. One of: a space <uuid>{" "}
(that space's bucket), "none" (the
project-general, space-less bucket), or{" "}
"context" (the space derived from the
request context — resolved per-row on lists, or the single space on
member/team/conversation surfaces). The empty string and the legacy{" "}
general / null aliases are rejected (400).
Missing buckets read as 0.
}
Only honored when spaceId is an explicit space <uuid>.
When true, spaceReputation is the{" "}
subtree sum — the named space plus all of its
descendant spaces (the root space's own bucket included). Ignored for{" "}
"none"; not allowed with "context".
{isUser ? Deprecated — use the spaceReputation{" "}
object instead. The flat form of spaceReputation.spaceId.
Still accepted (the object wins if both are passed); removal is a later
major version. Accepts a space <uuid> or "none" only —{" "}
"context" is rejected (400) on this endpoint.
: Deprecated — use the spaceReputation{" "}
object instead. The flat form of spaceReputation.spaceId.
Still accepted (the object wins if both are passed); removal is a later
major version. Accepts a space <uuid>, "none", or{" "}
"context".
}
Deprecated — use{" "}
spaceReputation.includeDescendants instead. The flat form,
only honored alongside an explicit spaceReputationId<uuid>.
;
};
## Overview
`useFetchManyComments` returns a function that fetches one level of a comment thread ([`GET /comments`](/v8/api-reference/comments/fetch-many-comments)): an entity's top-level comments (`entityId`) or a comment's direct replies (`parentId`). It's the fetch function behind `useEntityComments` and `useReplies`. Use it directly when you need full control over a thread request.
For a user's comments across entities, use [`useFetchCommentsByUserId`](/v8/hooks/comments/use-fetch-comments-by-user-id).
## Usage Example
```tsx theme={null}
import { useFetchManyComments, type Comment } from "@sublay/react-js";
import { useEffect, useState } from "react";
function TopComments({ entityId }: { entityId: string }) {
const fetchComments = useFetchManyComments();
const [comments, setComments] = useState([]);
const [cursor, setCursor] = useState(null);
useEffect(() => {
fetchComments({
entityId,
sortBy: "top",
limit: 10,
include: "user",
replyDepth: 1, // also bring each comment's first replies
replyLimit: 2,
}).then((res) => {
setComments(res.data);
setCursor(res.pagination.nextCursor);
});
}, [entityId]);
const loadMore = async () => {
if (!cursor) return;
const res = await fetchComments({ entityId, sortBy: "top", limit: 10, cursor, include: "user" });
setComments((prev) => [...prev, ...res.data]);
setCursor(res.pagination.nextCursor);
};
return (
<>
{comments.map((c) =>
{c.content}
)}
{cursor && }
);
}
```
## Parameters
One of `entityId` or `parentId` is required.
Fetch this entity's top-level comments.
Fetch this comment's direct replies.
How many comments at the level being fetched. Server default `10`, max `100`.
`pagination.nextCursor` from the previous response. Omit for the first page. Send the same sort as the request that returned it.
`"createdAt"`, `"top"` (raw count of `sortByReaction`) or `"controversial"`. Server default `"createdAt"`. `"new"` / `"old"` are deprecated aliases for `"createdAt"`.
Applies to every sort. Server default `"desc"`.
With `sortBy: "top"` only: the reaction to rank by. Server default `"upvote"`.
Levels of replies to nest under each returned comment (`0`–`5`). Server default `0`.
Replies per comment in the nested levels (at least `1`). Server default `3`.
Sort for the nested levels: `"createdAt"`, `"top"` or `"controversial"`. Defaults to `sortBy`.
Sort direction for the nested levels. Defaults to `sortDir`.
The reaction the nested levels rank by, when their sort is `"top"`.
Related data to populate, at every level.
A request can return at most 500 comments, nested replies included — see [Request size limit](/v8/api-reference/comments/fetch-many-comments#request-size-limit).
## Returns
A `Promise>`:
The comments at the requested level. With `replyDepth` above `0`, each carries nested `replies` (`{ data, pagination }`). When `spaceReputation` is requested, each embedded author carries an added `spaceReputation` number. See [Reputation](/v8/data-models/reputation).
Pass as `cursor` to get the next page. `null` when there's nothing more.
Whether more comments exist after this page.
See [Fetch Many Comments](/v8/api-reference/comments/fetch-many-comments) for placeholders, block flags and how to continue nested replies.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.