> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Add a Comment to a Ticket

> Add a comment to a ticket through the API Bridge, typically a link to the corresponding session in the Syteca monitoring results.

`/add-ticket-comment` writes a comment back to the ticket — typically a link to the corresponding place in the monitoring results on the Management Tool, so the reviewer can jump straight to the recorded session. All three fields (`sessionId`, `ticketId`, `ticketComment`) are required.

<Info>
  This endpoint is shown for reference. There is no Syteca-hosted server to call, so no live request panel is available.
</Info>


## OpenAPI

````yaml api-spec/api-bridge-openapi.yaml POST /add-ticket-comment
openapi: 3.0.0
info:
  version: '1.0'
  title: Syteca Ticketing System Integration API Bridge
  description: >
    The interface that a Syteca API Bridge service must implement. The API
    Bridge is a REST service that you build and host yourself to connect Syteca
    to any ticketing system. This specification has no servers URL, so the
    endpoint documentation renders in simple mode (no live request panel) — your
    Bridge runs at your own address and port.
servers: []
security: []
tags:
  - name: bridge
    description: Endpoints the API Bridge must implement for Syteca to call.
paths:
  /add-ticket-comment:
    post:
      tags:
        - bridge
      summary: Add a comment to a ticket
      description: >
        Adds a comment to the ticket, typically a link to the corresponding
        place in the monitoring results on the Management Tool.
      operationId: addTicketComment
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - sessionId
                - ticketId
                - ticketComment
              properties:
                sessionId:
                  type: string
                  example: f3a9c2e1-7b44-4d8e-9c2a-1e6b5d0f8a23
                ticketId:
                  type: string
                  example: INC0012345
                ticketComment:
                  type: string
                  example: 'Session recording: https://syteca.example.com/sessions/8842'
      responses:
        '201':
          description: Created. The comment was added.
        '401':
          description: Unauthorized (invalid session).
        '404':
          description: A ticket with the specified ID was not found.
        default:
          description: Unexpected error.

````