# Delete a comment

> Markdown version of https://docs.postlake.dev/api/delete-comments-by-id . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

`DELETE /v1/comments/{id}`

Take a comment down for good. Facebook cannot hide a Page's own comment, so this is how you retract one you posted. A failure means it is still there.

## Request

Authenticate with a bearer API key. Agents calling over MCP authorise with OAuth instead and never handle the key.

```bash
curl -X DELETE https://api.postlake.dev/v1/comments/{id} \
  -H "Authorization: Bearer $POSTLAKE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"account":"…"}'
```

### Parameters

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `id` | string | Yes | In the URL. The comment id |

### Body

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `account` | string | Yes | The connection the post is on |


## Response

Success (`200`).

| Field | Type | Required | What it is |
| --- | --- | --- | --- |
| `account` | string | No |  |
| `platform` | string | No |  |
| `ok` | boolean | No |  |



### Example

```json
{
  "account": "…",
  "platform": "…",
  "ok": false
}
```


## Calling this from an agent

Agents do not call REST. They call tools. Over the hosted MCP server this operation is `read_comments`, and the agent authorises with OAuth so your API key is never pasted into a chat or seen by the model. You control what any one agent may do: which brands it may act for, which networks it may reach, how much a day, and whether it may spend credits bought up front.

## Errors

Every failure uses one shape: a stable `type`, a granular `code`, the field at fault in `param`, and a plain-language `fix`. See https://docs.postlake.dev/errors.md .

Retries are safe: send the same `Idempotency-Key` and a call that already succeeded returns its original result rather than repeating it.

## Common questions

**Can an AI agent do this without the REST API?**

Yes. Over MCP the same job is the read_comments tool. The agent authorises with OAuth, so no API key is pasted into a chat or seen by the model, and the answer comes back in the same normalised shape.

**Is it safe to retry this call?**

Yes. Send the same Idempotency-Key and a call that already succeeded returns its original result instead of repeating the work. That is what makes it safe to hand to an agent that retries on its own.

**What happens when it fails?**

You get one error shape: a stable type, a granular code you can branch on, the offending field in param, and a fix written so an agent can correct itself rather than stop. Full list on Errors and retries.

## Related

- [What happened across every network](https://docs.postlake.dev/api/get-notifications.md) `GET /v1/notifications`
- [Replies on a post you published](https://docs.postlake.dev/api/get-posts-by-id-comments.md) `GET /v1/posts/{id}/comments`
- [Who follows a connected account](https://docs.postlake.dev/api/get-social-accounts-by-id-followers.md) `GET /v1/social-accounts/{id}/followers`
- [Who a connected account follows](https://docs.postlake.dev/api/get-social-accounts-by-id-following.md) `GET /v1/social-accounts/{id}/following`