<!-- Generated from the canonical Teloring documentation source. Do not edit this file. -->

Canonical page: https://docs.teloring.com/api/delete-message
Last modified: 2026-08-20T20:52:05.000Z

# Delete a message

import MethodEndpoint from "@theme/ApiExplorer/MethodEndpoint";
import ParamsDetails from "@theme/ParamsDetails";
import RequestSchema from "@theme/RequestSchema";
import StatusCodes from "@theme/StatusCodes";
import OperationTabs from "@theme/OperationTabs";
import TabItem from "@theme/TabItem";
import Heading from "@theme/Heading";
import Translate from "@docusaurus/Translate";

<Heading
  as={"h1"}
  className={"openapi__heading"}
  children={"Delete a message"}
>
</Heading>

<MethodEndpoint
  method={"delete"}
  path={"/conversations/{conversation_id}/messages/{message_id}"}
  context={"endpoint"}
>
  
</MethodEndpoint>



Remove one message from a conversation.

There is no equivalent in the console — this is API-only, and it is genuinely
destructive. It deletes **our** record of the message, not the copy the customer
already received on WhatsApp, SMS or email. Use it to redact something that
should never have been stored, not to "unsend".

The conversation's message count is corrected and attachments are detached from
the Files Warehouse index. Every delete is written to the audit log with the
credential that made it.

<Heading
  id={"request"}
  as={"h2"}
  className={"openapi-tabs__heading"}
>
  <Translate id="theme.openapi.request.title">Request</Translate>
</Heading>

<ParamsDetails
  {...require("./delete-message.ParamsDetails.json")}
>
  
</ParamsDetails>

<RequestSchema
  {...require("./delete-message.RequestSchema.json")}
>
  
</RequestSchema>

<StatusCodes
  {...require("./delete-message.StatusCodes.json")}
>
  
</StatusCodes>
