> ## 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.

# Request a Session ID

> Establish a session with the ticketing system through the API Bridge and receive a session ID for subsequent calls.

`/connect` is the first endpoint Syteca calls. Your API Bridge establishes a session with the ticketing system and returns a `sessionId` that the [ticket status](/docs/api/integrations/ticket-status) and [add comment](/docs/api/integrations/add-ticket-comment) calls then use.

The request body is optional. If your ticketing system needs connection details, accept them in the optional `connectionString` field.

<Info>
  This endpoint is shown for reference. There is no Syteca-hosted server to call — your Bridge runs at your own address and port — so no live request panel is available.
</Info>


## OpenAPI

````yaml api-spec/api-bridge-openapi.yaml POST /connect
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:
  /connect:
    post:
      tags:
        - bridge
      summary: Request a session ID
      description: >
        Establishes a session with the ticketing system and returns a session ID
        that subsequent calls use. The request body is optional.
      operationId: connect
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                connectionString:
                  type: string
                  description: Optional connection string for the ticketing system.
                  example: Server=tickets.local;Db=helpdesk
      responses:
        '200':
          description: A JSON object including the session ID.
          content:
            application/json:
              schema:
                type: object
                properties:
                  sessionId:
                    type: string
                    example: f3a9c2e1-7b44-4d8e-9c2a-1e6b5d0f8a23
        '422':
          description: Unprocessable Entity (wrong connection string).
        default:
          description: Unexpected error.

````