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

# Push a vulnerability to a tracker

> Creates an issue for the vulnerability in your organization’s connected Linear or Jira workspace, the same as Push to Linear or Push to Jira on the vulnerability page, and returns the issue’s key and URL. Requires the admin role; API keys act as admins. Connect the tracker first under Settings → Integrations.

Pushing is idempotent: pushing the same vulnerability to the same tracker again returns the issue the first push created.

Errors use these codes: `tracker_not_connected` (409) when the tracker isn’t connected, `not_found` (404) for an ID outside your organization, and `tracker_unavailable` (502) when the tracker couldn’t be reached. Retry a 502 after checking the connection.



## OpenAPI

````yaml /reference/openapi.yaml post /vulnerabilities/{id}/tracker-issue
openapi: 3.1.0
info:
  title: Antigen API
  version: v1
  description: >-
    Work with the same agents, runs, and resources your team uses in Antigen.
    Requests and responses use camelCase fields. List endpoints return arrays.
    See the [overview](/reference) for authentication, updates, and errors.
servers:
  - url: https://api.antigen.sh/v1
security:
  - ApiKeyAuth: []
  - SessionAuth: []
tags:
  - name: Agents
    description: Retrieve, compose, and register agent configurations.
  - name: Models
    description: Models available to agents in your organization.
  - name: Targets
    description: Submit testing scope for human approval.
  - name: Runs
    description: Execute agents and control their work.
  - name: Vulnerabilities
    description: Track weaknesses, remediation, status, and assignment.
  - name: Evidence
    description: Read supporting file metadata and retrieve file contents.
  - name: Reports
    description: Read and export captured engagement results.
  - name: Human tasks
    description: Ask people for help and follow their responses.
  - name: Hooks
    description: Connect status and assignment changes to your own service.
  - name: Asset Map
    description: Read your organization’s infrastructure graph.
  - name: Integrations
    description: Inspect and disconnect provider connections.
  - name: Team
    description: List the people vulnerabilities can be assigned to.
  - name: API keys
    description: Create and revoke credentials for automation.
  - name: Account
    description: Identify the caller and end CLI sessions.
paths:
  /vulnerabilities/{id}/tracker-issue:
    post:
      tags:
        - Vulnerabilities
      summary: Push a vulnerability to a tracker
      description: >-
        Creates an issue for the vulnerability in your organization’s connected
        Linear or Jira workspace, the same as Push to Linear or Push to Jira on
        the vulnerability page, and returns the issue’s key and URL. Requires
        the admin role; API keys act as admins. Connect the tracker first under
        Settings → Integrations.


        Pushing is idempotent: pushing the same vulnerability to the same
        tracker again returns the issue the first push created.


        Errors use these codes: `tracker_not_connected` (409) when the tracker
        isn’t connected, `not_found` (404) for an ID outside your organization,
        and `tracker_unavailable` (502) when the tracker couldn’t be reached.
        Retry a 502 after checking the connection.
      operationId: pushVulnerabilityToTracker
      parameters:
        - name: id
          in: path
          required: true
          description: >-
            The vulnerability’s ID, or its key as shown in the platform, such as
            LRK-003.
          schema:
            type: string
            minLength: 1
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PushToTracker'
      responses:
        '200':
          description: Successful response.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TrackerIssue'
        '400':
          $ref: '#/components/responses/Error400'
        '401':
          $ref: '#/components/responses/Error401'
        '403':
          $ref: '#/components/responses/Error403'
        '404':
          $ref: '#/components/responses/Error404'
        '409':
          $ref: '#/components/responses/Error409'
        '429':
          $ref: '#/components/responses/Error429'
        '502':
          $ref: '#/components/responses/Error502'
components:
  schemas:
    PushToTracker:
      type: object
      properties:
        provider:
          type: string
          description: Tracker to create the issue in.
          enum:
            - linear
            - jira
      required:
        - provider
      additionalProperties: false
      example:
        provider: linear
    TrackerIssue:
      type: object
      properties:
        provider:
          type: string
          description: Tracker the issue is in.
          enum:
            - linear
            - jira
        externalKey:
          type: string
          description: The issue’s key in the tracker, such as ENG-123.
          minLength: 1
        url:
          type: string
          format: uri
          description: Link to the issue in the tracker.
      required:
        - provider
        - externalKey
        - url
      additionalProperties: false
      example:
        provider: linear
        externalKey: ENG-123
        url: https://linear.app/acme/issue/ENG-123
    Error:
      type: object
      properties:
        error:
          type: object
          properties:
            code:
              type: string
              description: Stable error code.
            message:
              type: string
              description: Description of the problem.
          required:
            - code
            - message
          additionalProperties: false
      required:
        - error
      additionalProperties: false
      example:
        error:
          code: invalid_request
          message: The target value is required.
  responses:
    Error400:
      description: Invalid request
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: invalid_request
              message: Check the request fields and values.
    Error401:
      description: Authentication required
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: unauthorized
              message: Supply a valid API key or session token.
    Error403:
      description: Permission denied
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: forbidden
              message: >-
                Your role does not permit this operation, or the requested work
                is outside approved scope.
    Error404:
      description: Resource not found
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: not_found
              message: The resource does not exist in this organization.
    Error409:
      description: Conflict
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: conflict
              message: The resource’s current state does not allow this operation.
    Error429:
      description: Too many requests
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: rate_limited
              message: Retry after the interval in Retry-After.
      headers:
        Retry-After:
          description: Seconds to wait before retrying.
          schema:
            type: integer
            minimum: 1
    Error502:
      description: Upstream service unavailable
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: tracker_unavailable
              message: Unable to push to Linear. Check the connection and try again.
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        API key from your organization, for CI pipelines and other automated
        systems. Supply the value directly, without a Bearer prefix. A key acts
        as an admin of its organization. When a request carries both a key and a
        session, the key is used.
    SessionAuth:
      type: http
      scheme: bearer
      description: >-
        Session token from `antigen login`, sent in the `Authorization` header
        with the `Bearer` scheme. The request acts as the signed-in member, with
        their own role in their organization. Sessions stop working when the
        member is deactivated.

````

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