Strategic Tickets

Add a ticket comment

Changed on

Add an entry to a ticket's thread, written in Markdown. The entry is recorded as written by an API key. A thread holds at most 500 entries. Requires a read_write key.

post/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

Request body

bodystring required

The entry's text, in Markdown. At most 20000 characters. It is stored exactly as it is sent — leading whitespace is a code block in the dialect that draws it, so nothing is trimmed off the ends.

Example request

{
  "body": "Reached the editor on 14 Sep; they update the guide quarterly."
}

Response

Example response

{
  "item": {
    "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

    • info

      removed the non-success response with the status

    • 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