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

# Create a tracker ticket

> Create a tracker ticket in a project. When
`customerEmail` is set, the customer is added as the first upvoter
(`upvotes: [{ email, name }]`, `upvotesCount: 1`) and their session
(source ticket's session, else resolved by email) becomes the ticket's
creator `session` — used for feature requests where the originating
customer should own the request like a portal-submitted one.

Feature requests filed by an agent (`createdByAgent` set) are created as
ordinary customer requests linked to their conversation, NOT as tracker
tickets — only human/dashboard creates get `trackerTicket: true`.

A feature request that strongly matches existing ones is refused with a
409 `DUPLICATE_FEATURE_REQUEST` listing them in `candidates` (best first;
`duplicate` is the best one). Repeat the call with their ids in
`notDuplicateOf` when they are a different need.



## OpenAPI

````yaml https://api.gleap.io/api-docs.json post /tickets/tracker-tickets
openapi: 3.0.0
info:
  title: gleap-server
  version: 14.0.0
  contact: {}
servers:
  - url: https://api.gleap.io/v3
security: []
paths:
  /tickets/tracker-tickets:
    post:
      tags:
        - Ticket
      summary: Create a tracker ticket
      description: >-
        Create a tracker ticket in a project. When

        `customerEmail` is set, the customer is added as the first upvoter

        (`upvotes: [{ email, name }]`, `upvotesCount: 1`) and their session

        (source ticket's session, else resolved by email) becomes the ticket's

        creator `session` — used for feature requests where the originating

        customer should own the request like a portal-submitted one.


        Feature requests filed by an agent (`createdByAgent` set) are created as

        ordinary customer requests linked to their conversation, NOT as tracker

        tickets — only human/dashboard creates get `trackerTicket: true`.


        A feature request that strongly matches existing ones is refused with a

        409 `DUPLICATE_FEATURE_REQUEST` listing them in `candidates` (best
        first;

        `duplicate` is the best one). Repeat the call with their ids in

        `notDuplicateOf` when they are a different need.
      operationId: CreateTrackerTicket
      parameters:
        - in: header
          name: project
          required: true
          schema:
            type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              properties:
                createdByAgent:
                  properties:
                    sourceTicketId:
                      type: string
                    agentName:
                      type: string
                    agentId:
                      type: string
                  required:
                    - agentName
                  type: object
                  description: >-
                    Provenance for agent-created tickets ("Created by Kai from
                    #123").
                notDuplicateOf:
                  items:
                    type: string
                  type: array
                  description: >-
                    Ids of existing feature requests (from a duplicate
                    response's

                    `candidates`) that are a different need than this one, e.g.
                    the same

                    feature on another product surface. The duplicate check
                    skips them.
                skipDuplicateCheck:
                  type: boolean
                  description: >-
                    Dashboard creates pass true (humans already saw duplicate

                    suggestions in the modal). Agent/MCP creates must NOT set
                    this —

                    the server-side duplicate guard is what keeps agents from
                    filing

                    the same request twice.
                customerName:
                  type: string
                customerEmail:
                  type: string
                linkedTicketIds:
                  items:
                    type: string
                  type: array
                description:
                  type: string
                title:
                  type: string
                type:
                  type: string
              type: object
      responses:
        '200':
          description: Ok
          content:
            application/json:
              schema: {}
      security:
        - jwt: []
components:
  securitySchemes:
    jwt:
      type: http
      scheme: bearer
      bearerFormat: JWT

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.