> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/api/reference/comments/deletecomment.md).

# Delete a comment

Delete a comment with the FLORA API: DELETE /projects/{projectId}/comment-threads/{threadId}/comments/{commentId}.

Soft-deletes one live comment. The caller can delete their own comments, or a FLORA comment they posted. Thread managers can also delete FLORA comments, including ones posted before Flora stored an acting user. Deleting the last live comment resolves the thread and sets `thread_resolved` to true. Already-deleted comments, comments in another thread, and inaccessible projects return 404. Comments owned by someone else return `forbidden`. Mutating public API requests support an optional Idempotency-Key header for client retries; duplicate keys within two hours return idempotency\_duplicate.

```http
DELETE https://app.flora.ai/api/v1/projects/{projectId}/comment-threads/{threadId}/comments/{commentId}
```

* **Auth:** API key as a bearer token, `Authorization: Bearer $FLORA_API_KEY`. See [Authentication](/api/platform/authentication.md).
* **TypeScript SDK:** `client.projects.comments.deleteComment()`.
* **Idempotency:** optional `Idempotency-Key` header. See [Idempotency](/api/platform/idempotency.md).
* **Operation ID:** `deleteComment`.

## Example

{% tabs %}
{% tab title="cURL" %}

```bash
curl -X DELETE 'https://app.flora.ai/api/v1/projects/prj_abc123/comment-threads/cth_abc123/comments/cmt_abc123' \
  -H "Authorization: Bearer $FLORA_API_KEY"
```

{% endtab %}

{% tab title="TypeScript SDK" %}

```typescript
import { FloraClient } from '@flora-ai/flora';

const client = new FloraClient({ apiKey: process.env['FLORA_API_KEY'] });

const comment = await client.projects.comments.deleteComment({
  projectId: 'prj_abc123',
  threadId: 'cth_abc123',
  commentId: 'cmt_abc123',
});
console.log(comment);
```

{% endtab %}
{% endtabs %}

## Path parameters

| Name        | Type   | Required | Description                                                             |
| ----------- | ------ | -------- | ----------------------------------------------------------------------- |
| `projectId` | string | Yes      | Project identifier. Pattern: `^prj_\S+$`. Example: `prj_abc123`.        |
| `threadId`  | string | Yes      | Comment thread identifier. Pattern: `^cth_\S+$`. Example: `cth_abc123`. |
| `commentId` | string | Yes      | Comment identifier. Pattern: `^cmt_\S+$`. Example: `cmt_abc123`.        |

## Responses

### 200: Comment deleted.

| Field             | Type    | Required | Description                                                                   |
| ----------------- | ------- | -------- | ----------------------------------------------------------------------------- |
| `comment_id`      | string  | Yes      | Comment identifier. Pattern: `^cmt_\S+$`. Example: `cmt_abc123`.              |
| `deleted`         | boolean | Yes      | Always true when the comment was deleted. Always `true`.                      |
| `thread_resolved` | boolean | Yes      | True when deleting this comment left no live comments and resolved the thread |

## Errors

Every error has the same body: `error.code`, `error.message`, and `error.fields` on validation errors. See [Errors](/api/platform/errors.md) for how to recover from each code.

| Status | Code                                         | Meaning                                                                             |
| ------ | -------------------------------------------- | ----------------------------------------------------------------------------------- |
| 400    | `invalid_json`, `input_validation_error`     | The body isn't valid JSON, or an input failed validation (`fields` lists each one). |
| 401    | `unauthorized`, `invalid_api_key`            | The API key is missing, invalid or revoked.                                         |
| 402    | `insufficient_credits`                       | The workspace balance is too low for this request.                                  |
| 403    | `forbidden`, `paid_plan_required`            | The key can't do this, or the workspace plan doesn't include it.                    |
| 404    | `not_found`                                  | The resource doesn't exist or isn't visible to this key.                            |
| 409    | `idempotency_duplicate`, `revision_conflict` | Duplicate `Idempotency-Key` or a stale `base_revision`.                             |
| 429    | `rate_limited`                               | Too many requests. Back off and retry.                                              |
| 500    | `unknown_error`, `internal_error`            | Something failed on FLORA's side. Retry with backoff.                               |
| 503    | `temporarily_unavailable`                    | Authorization is temporarily unavailable. Retry later.                              |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flora.ai/api/reference/comments/deletecomment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.