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

# Delete a comment.

> Authorship, not permission tier, is the gate: you may delete your own
comment, and holders of `issues:close` may moderate anyone's — someone has to
be able to remove a departed colleague's. A bare API-key call carries no
human identity and so cannot prove authorship; it needs `issues:close`.

The delete is soft. The comment stays in the thread as a tombstone with
`body: null` rather than vanishing. Returns 204 with no body.



## OpenAPI

````yaml /reference/openapi.json delete /issues/{iid}/comments/{cid}
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:
  /issues/{iid}/comments/{cid}:
    delete:
      tags:
        - Issues
      summary: Delete a comment.
      description: >-
        Authorship, not permission tier, is the gate: you may delete your own

        comment, and holders of `issues:close` may moderate anyone's — someone
        has to

        be able to remove a departed colleague's. A bare API-key call carries no

        human identity and so cannot prove authorship; it needs `issues:close`.


        The delete is soft. The comment stays in the thread as a tombstone with

        `body: null` rather than vanishing. Returns 204 with no body.
      operationId: delete_comment
      parameters:
        - name: iid
          in: path
          description: The issue's id.
          required: true
          schema:
            type: string
            format: uuid
        - name: cid
          in: path
          description: The comment's id.
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '204':
          description: Comment tombstoned.
        '401':
          description: Missing, unknown, or disabled key.
        '403':
          description: >-
            The key lacks `issues:read`, or you are not the comment's author and
            lack `issues:close`.
        '404':
          description: No such issue or comment in this organization.
      security:
        - api_key: []
components:
  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.

````