DELETE
Delete a conversation (delete-for-me)

Overview

Performs a per-user “delete for me”: the conversation is hidden from the caller’s inbox only. The other participant still sees the conversation and its full message history. No messages are ever destroyed. This matches the standard chat-app delete-for-me semantics:
  • The conversation disappears from GET /chat/conversations for the caller.
  • The peer’s inbox is unchanged.
  • All messages remain readable via list-messages (the gate is participation, not the clear marker).
  • The conversation reappears in the caller’s inbox automatically if a newer message arrives after the delete (i.e. lastMessageAt > clearedAt).
Internally this stamps a clearedAt timestamp on the caller’s participantState entry; it does not delete the conversations row or any messages rows.
There is intentionally no “delete for everyone” / hard-delete endpoint. Deletion is always scoped to the calling user.

Authentication

Bearer <accessToken> required. requireOnboarded middleware applied.

Path parameters

Query parameters

None.

Request body

None.

Response — 204 No Content

Empty body. The call is idempotent — deleting an already-deleted conversation re-stamps clearedAt and still returns 204.

Error responses

Side effects

  • Sets clearedAt (server time) on the caller’s participantState entry.
  • No change to the peer’s participantState, the conversations row’s status, or any messages.

Bulk delete

There is no bulk endpoint — to delete several conversations the client issues one DELETE per conversation (the mobile app’s multi-select “trash” action loops over the selected ids). Each call is independent and idempotent.

See also

  • List conversations — the inbox this endpoint hides a row from.
  • Get conversation — still returns the conversation (delete is inbox-scoped, not an access revocation).
  • Block a user — a stronger action that prevents future messaging in both directions.

curl