List comments (keyset pagination)
List comments for a parent entity using cursor-based pagination, whose cost per page does not grow with depth. This is the endpoint for walking a long thread: GET /comments rejects an offset above 200 and points here.
Pass the next_cursor from a response as after_cursor to get the following page; its absence means the walk is complete. offset is not accepted. Sorting is limited to id (default) and createdAt, the columns that do not change under an in-flight walk — a cursor over a mutable column would skip or repeat rows.
get_positions and holders_only are not available here; both are per-author balance lookups whose cost scales with the page rather than the cursor. Use GET /comments if you need them.
Request
- Base URL: https://gamma-api.polymarket.com (the document declares no server; this is the origin it was published from)
- URL: https://gamma-api.polymarket.com/comments/keyset
- Auth: none declared
Query parameters
Parent entity ID
Parent entity type
Max results returned; values above 100 are clamped to 100
Not allowed for keyset pagination; rejected by the application layer
Field to sort by. Only immutable columns are seekable; defaults to id.
Sort ascending when true (default true)
Opaque keyset cursor from a previous response
Response
OK
Example response
{
"$schema": "https://example.com/schemas/CommentsKeysetListResponse.json",
"comments": [
{
"$schema": "https://example.com/schemas/Comment.json",
"reactions": [
{
"$schema": "https://example.com/schemas/Reaction.json"
}
]
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.