Skip to main content

​
How comments work

Comments allow attendees and visitors to discuss an event. Each comment is tied to a specific event and can optionally be a reply to another comment, enabling threaded conversations.The CommentDto includes a parentId field. When parentId is null, the comment is a top-level post. When parentId references another comment’s ID, it is a reply. The replies list on each CommentDto contains all direct child comments.

​
Comment fields

FieldTypeDescription
idGuidUnique comment identifier.
userIdstringID of the user who posted the comment.
userNamestringDisplay name of the commenter.
userMembershipMembershipDtoActive membership of the commenter, if any.
eventIdGuidID of the event this comment belongs to.
eventTitlestringTitle of the event.
contentstringText body of the comment.
publicationDateDateTimeWhen the comment was posted.
parentIdGuid?ID of the parent comment, or null for top-level posts.
repliesCommentDto[]Direct replies to this comment.

​
Posting a comment

POST /api/comments

{
  "userId": "user-id-string",
  "eventId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "content": "Looking forward to this event!",
  "parentId": null
}
To post a reply, set parentId to the id of the comment you are replying to.
{
  "userId": "user-id-string",
  "eventId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "content": "See you there!",
  "parentId": "parent-comment-id"
}

​
Editing a comment

PUT /api/comments/{id}

{
  "content": "Updated comment text."
}

​
Deleting a comment

DELETE /api/comments/{id}
Only the User, Organizer, or Admin roles can create, edit, or delete comments. Reading comments is public via GET /api/comments and GET /api/comments/{id}.

Build docs developers (and LLMs) love

Get started for freeTalk to us