## Delete a comment

**delete** `/v2/comment`

Deletes a comment using the legacy Clover API format.

This endpoint accepts the comment ID in the request body instead of the route parameter.

### Request Body

```json
{
  "id": "507f1f77bcf86cd799439011"
}
```

### Deletion Behavior

- **Comments with replies**: Soft delete

  - Content is replaced with "[deleted]"
  - Author information is anonymized
  - Comment remains visible to maintain conversation context
  - Votes and scores are reset to 0

- **Comments without replies**: Hard delete

  - Comment is permanently removed from the database
  - All associated data is deleted

### Permissions

- Comment authors can delete their own comments
- Admins can delete any comment (subject to permissions)
- Lite seat admins can only delete their own comments
- Non-authors require `manage_comments` or `manage_comments_private` permission

### Response

Returns a success confirmation (Clover format):

```json
{
  "success": true
}
```

Note: Nova API returns `{ id, object: "comment", deleted: true }`, but Clover transformer converts it to `{ success: true }` for backwards compatibility.

### Errors

- `400` - Invalid comment ID format or missing ID in body
- `403` - Not authorized to delete this comment
- `404` - Comment not found or doesn't belong to your organization

### Header Parameters

- `"Featurebase-Version": optional "2026-01-01.nova" or "2025-12-12.clover"`

  - `"2026-01-01.nova"`

  - `"2025-12-12.clover"`

### Body Parameters

- `id: string`

  Comment ID

### Returns

- `success: boolean`

### Example

```http
curl https://do.featurebase.app/v2/comment \
    -X DELETE \
    -H "Authorization: Bearer $FEATUREBASE_API_KEY"
```

#### Response

```json
{
  "success": true
}
```