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

# Get the Ticket Status

> Validate that a ticket exists and is not closed through the API Bridge. Returns status 0 (not found), 1 (active), or 2 (closed).

`/ticket-status` validates the ticket number a user entered at login. Syteca calls it with the `sessionId` from [`/connect`](/docs/api/integrations/connect) and the `ticketId` the user provided. Your Bridge returns the ticket's numeric status.

The status values are:

| Status | Meaning                             |
| ------ | ----------------------------------- |
| `0`    | Ticket not found                    |
| `1`    | Ticket active — log on is permitted |
| `2`    | Ticket closed — log on is denied    |

<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 GET /ticket-status
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:
  /ticket-status:
    get:
      tags:
        - bridge
      summary: Get the ticket status
      description: >
        Validates that a ticket exists and is not closed. Returns the ticket ID
        and its numeric status (0 = not found, 1 = active, 2 = closed).
      operationId: ticketStatus
      parameters:
        - name: sessionId
          in: query
          required: true
          description: The session ID returned by /connect.
          schema:
            type: string
          example: f3a9c2e1-7b44-4d8e-9c2a-1e6b5d0f8a23
        - name: ticketId
          in: query
          required: true
          description: The ticket number entered by the user at login.
          schema:
            type: string
          example: INC0012345
      responses:
        '200':
          description: A JSON object including the ticket ID and status.
          content:
            application/json:
              schema:
                type: object
                properties:
                  ticketId:
                    type: string
                    example: INC0012345
                  status:
                    type: number
                    description: 0 = not found, 1 = active, 2 = closed.
                    example: 1
        '401':
          description: Unauthorized (invalid session).
        '404':
          description: A ticket with the specified ID was not found.
        default:
          description: Unexpected error.

````