Skip to main content
GET
Get task comments

Overview

Retrieve all comments for a specific task. Comments are returned in descending order (newest first) with relative timestamps based on the user’s timezone.

Path Parameters

integer
required
The unique identifier of the task to retrieve comments for.Example: 456

Response

Returns an array of comment objects.
integer
The unique identifier of the comment.
integer
The ID of the task this comment belongs to.
integer
Reference ID (same as task_id).
integer
The ID of the user who created the comment.
integer
The ID of the team.
string
The comment text.
string
The type of comment.
object
Reaction data object containing reaction counts and users.
array
Array of users who reacted to this comment (extracted from reaction object for convenience).
string
Human-readable relative time since the comment was posted.Formats:
  • "X second ago" - Less than 1 minute
  • "X minutes ago" - 1 minute to 1 hour
  • "X hours X minutes ago" - 1 hour to 12 hours
  • "DD/MMM/YYYY HH:MM AM/PM" - More than 12 hours
string
The timestamp when the comment was created (ISO 8601 format).
string
The timestamp when the comment was last updated (ISO 8601 format).

Example Request

Example Request (JavaScript)

Example Response

Example Response - Empty Comments

Time Display Format

The time field is calculated based on the user’s timezone and displays in the following formats:

Error Responses

Notes

  • Timezone awareness: All timestamps are converted to the user’s timezone for display
  • Descending order: Comments are returned with the newest first (DESC order by ID)
  • Empty arrays: If a task has no comments, an empty array [] is returned
  • Reaction data: Each comment includes full reaction data and a convenient reactedUsers array
  • HTML support: Comments may contain HTML formatting
  • Relative time: The time field provides human-readable timestamps
  • User timezone: Timestamps are automatically adjusted to match the authenticated user’s timezone setting
  • No pagination: All comments are returned in a single response (consider pagination for tasks with many comments)

Use Cases

  • Display comment history: Show all discussion on a task
  • Track updates: See who commented and when
  • Review reactions: Check which comments received reactions
  • Timeline view: Build a timeline of task discussions
  • Notification context: Provide context for comment notifications

Best Practices

  • Cache comment data when possible to reduce API calls
  • Refresh comment list after adding/updating/deleting comments
  • Display reactions inline for better user engagement
  • Consider implementing pagination for tasks with many comments
  • Handle empty comment arrays gracefully in your UI
  • Use the time field for display, but created_at for sorting/filtering

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

taskId
integer<int64>
required

The unique identifier of the task

Example:

456