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

# Open an issue against an existing alert, by hand.

> `summary` is required and capped at 2000 characters; `title` is optional and
defaults to the alert's own name.

An alert can have only one open issue at a time, so this does NOT always
create a row: if one is already open, your summary folds into it and the
response is **200** with `newly_opened: false`. **201** means a new issue was
really opened. Read that field rather than assuming. `source` in the response
is the value actually stored — re-posting against an issue the dispatcher or
an audit opened leaves its provenance alone.



## OpenAPI

````yaml /reference/openapi.json post /alerts/{id}/issues
openapi: 3.1.0
info:
  title: AgentEye API
  description: >-
    The AgentEye observability API.


    Every path below is relative to `/v1` on your deployment's dashboard origin
    — e.g. `https://app.example.com/v1/sessions`. Authenticate with a scoped API
    key as a bearer token.


    Organization scoping: a key belongs to one organization and acts on it
    automatically. An instance-scoped key selects one per request with the
    `X-AgentEye-Org` header; without it, such a key resolves to the default
    organization, so set it explicitly on a multi-org deployment.
  license:
    name: MIT
    identifier: MIT
  version: 0.0.1-beta.77
servers:
  - url: /v1
    description: This deployment
security:
  - api_key: []
tags:
  - name: Events
    description: Ingest and query the event store.
  - name: Sessions
    description: Agent sessions and their evaluations.
  - name: Evaluations
    description: Evaluation results and re-runs.
  - name: Dashboards
    description: Dashboards and their tiles.
  - name: Queries
    description: Saved SQL and ad-hoc query execution.
  - name: Keys
    description: Mint and manage scoped API keys.
  - name: Users
    description: Dashboard members and access.
  - name: Settings
    description: Operational settings and context-window overrides.
  - name: Permission sets
    description: Named permission roles.
  - name: Alerts
    description: Alert rules and their recipients.
  - name: Issues
    description: Open, triage, assign and resolve issues.
  - name: Audits
    description: Recurring audits and their findings.
  - name: Usage
    description: Organization usage and billing windows.
  - name: Health
    description: Liveness.
  - name: Auth
    description: Describe the key you are calling with.
paths:
  /alerts/{id}/issues:
    post:
      tags:
        - Issues
      summary: Open an issue against an existing alert, by hand.
      description: >-
        `summary` is required and capped at 2000 characters; `title` is optional
        and

        defaults to the alert's own name.


        An alert can have only one open issue at a time, so this does NOT always

        create a row: if one is already open, your summary folds into it and the

        response is **200** with `newly_opened: false`. **201** means a new
        issue was

        really opened. Read that field rather than assuming. `source` in the
        response

        is the value actually stored — re-posting against an issue the
        dispatcher or

        an audit opened leaves its provenance alone.
      operationId: create_incident
      parameters:
        - name: id
          in: path
          description: The alert's id.
          required: true
          schema:
            type: string
            format: uuid
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateIncidentBody'
        required: true
      responses:
        '200':
          description: >-
            The alert already had an open issue; this folded into it
            (`newly_opened: false`).
        '201':
          description: A new issue was opened.
        '401':
          description: Missing, unknown, or disabled key.
        '403':
          description: The key lacks `issues:create`.
        '404':
          description: No such alert in this organization.
        '422':
          description: >-
            `summary` is missing or exceeds 2000 characters, or `title` exceeds
            200 characters.
      security:
        - api_key: []
components:
  schemas:
    CreateIncidentBody:
      type: object
      required:
        - summary
      properties:
        summary:
          type: string
        title:
          type:
            - string
            - 'null'
          description: |-
            Optional short title. Omitted/blank falls back to the parent alert's
            name, which is the line the UI used to synthesize at read time.
  securitySchemes:
    api_key:
      type: http
      scheme: bearer
      description: >-
        A scoped AgentEye API key. Mint one in the dashboard under Settings →
        API keys, or with `POST /v1/keys`. Each endpoint names the permission it
        requires; a key without it gets 403 and a `required_permission` field
        naming what was missing.

````