Strategic Tickets

List a ticket's comments

Changed on

List a ticket's thread, oldest first and whole — nothing pages it, so nothing is counted twice. Each entry says what wrote it: a person working in the app, or an API key.

get/v1/projects/{projectId}/tickets/{ticketId}/comments

Request

  • Base URL: https://api.competlab.com
  • URL: https://api.competlab.com/v1/projects/{projectId}/tickets/{ticketId}/comments
  • Auth: API key in header CL-API-Key

Path parameters

ticketIdstring required
Example:507f1f77bcf86cd799439011

Ticket ID

projectIdstring required
Example:507f1f77bcf86cd799439011

Project ID

Response

Example response

{
  "items": [
    {
      "id": "507f1f77bcf86cd799439021",
      "ticketId": "507f1f77bcf86cd799439011",
      "author": {
        "userId": "507f1f77bcf86cd799439011",
        "fullName": "Dana Ellis"
      },
      "body": "Reached the editor on 14 Sep; they update the guide quarterly.",
      "createdAt": "2026-09-15T10:05:00.000Z",
      "updatedAt": "2026-09-15T10:05:00.000Z",
      "briefing": {
        "runId": "6a3950c06bda450a1372048e",
        "editionNumber": 5,
        "completedAt": "2026-10-05T06:12:00.000Z"
      }
    }
  ]
}

Changes

  • c9dadd2d3a30Revision changes
    • info

      removed the non-success response with the status

  • b08f96c9300bRevision changes
    • warning

      added the new nothing_to_return enum value to the / response property for the response status

    • warning

      added the new paging_requires_compact_view enum value to the / response property for the response status

    • warning

      added the new paging_requires_summary enum value to the / response property for the response status

    • info

      added the required property // to the response with the status