---
title: "Delete a comment"
method: DELETE
path: "/inbox/threads/{id}/messages/{messageId}"
tags: ["Inbox"]
---

# Delete a comment

`DELETE /inbox/threads/{id}/messages/{messageId}`

## Request

- Base URL: `https://api.rizamo.com/v1`
- URL: `https://api.rizamo.com/v1/inbox/threads/{id}/messages/{messageId}`
- Auth: HTTP bearer

Deletes the comment from its network, as the account, with the replies under it, and from the thread: it no longer shows in `Get a thread`. When it is the thread's first comment (`first`), the thread goes too, and leaves every list and count. One already gone from the network counts as deleted, so a delete that failed can be asked again. Errors: 400, before any call, when it is not a comment (a message) or its network does not allow it for this comment, with why (`moderationProblem`); 422 `capability_missing` when the account's login does not allow managing comments (on Threads, until Meta approves Rizamo's access to replies); 409 when the account needs a new login or is not active, the reply is still sending, or the network refused, with its reason; 404 for a thread or comment the caller does not reach. On Threads, 422 too for the profile's own reply until Meta approves Rizamo's access to deletes.

## Path parameters

- `id` string, required: The thread's id (`thr_`).
- `messageId` string, required: The comment's message id (`msg_`), from Get a thread.

## Response `200`

OK

- object
  - `id` string, required: The comment deleted.
  - `threadDeleted` boolean, required: True when it was the thread's first comment: the thread is gone from the inbox with it.

## Other responses

- `400`: `invalid_request`: A field is missing or wrong, or the request cannot be done as asked: the message names the field or says what to change.
- `401`: `unauthorized`: No API key or sign-in, or the key does not work: it was deleted, or it expired.
- `403`: `forbidden`: The caller may not do this: the key or agent lacks the scope (the message names it), or the action needs another role or a fresh sign-in.
- `404`: `not_found`: No such object, or it is outside your team or the profiles your key reaches.
- `409`: `conflict`: The object's state does not allow it now, such as an account that needs a new login. `queue_empty`: A post with `queue: true` whose profile has no posting times: set them, or give a `scheduledAt`. `queue_full`: No posting time free for the post's accounts in the next 90 days: add times, or give a `scheduledAt`. `idempotency_key_in_use`: A request with this `Idempotency-Key` is still running: try again in a moment.
- `413`: `payload_too_large`: The body is over 1 MB: files go up through the upload links of `POST /v1/media`.
- `415`: `unsupported_media_type`: The body is not JSON: send it with `Content-Type: application/json`.
- `422`: `capability_missing`: The account cannot do this: see its `capabilities`. `idempotency_key_reused`: This `Idempotency-Key` was used for a different request in the last 24 hours: send a new key.
- `429`: `rate_limited`: Over one of Rizamo's limits, or a network asked Rizamo to slow down: wait for `Retry-After` seconds, or as long as the message says.
- `500`: `internal`: Our side failed: retry, and send the `requestId` if it keeps failing.
- `503`: `timeout`: The request took too long to work out, most often a report: try again in a moment, or ask a report for a shorter period or one profile.

---

[API](https://skmtc.dev/rizamo/apis/rizamo-api.md) - [All operations](https://skmtc.dev/rizamo/apis/rizamo-api/llms.txt) - [OpenAPI document](https://skmtc.dev/rizamo/apis/rizamo-api/revisions/31b0c1b1ffb5?raw)
