# Suppress Message

{% openapi src="/files/0awfCbIZtOPaANVs6Ftp" path="/v1/admin/messagesuppression/{id}/suppress" method="post" expanded="true" fullWidth="true" %}
[pod-api-public.yaml](https://544392450-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F909t04Fk8FiEI7fBcmlw%2Fuploads%2Fgit-blob-e56143a90f85b2a2e67b6c5a2db19a7b566d4ae2%2Fpod-api-public.yaml?alt=media)
{% endopenapi %}

### Suppressed Message Example

The following image shows how the UI represents a suppressed message.\
The image on the left shows the original message before being suppressed. The image on the right shows how the message will be displayed after being suppressed.

![](https://files.readme.io/a92e02e-suppressed.png)

As of Release v1.45, if the user attempts to suppress a message that has already been suppressed at an earlier point in time, the returned `suppressionDate` will have a value of 0, as shown below:

```json
{
    "messageId":"_Gj13MiR-5IrVtrmPNl6fn___qvWCYI_dA"
    "suppressed":true
    "suppressionDate":0
}
```

In addition, be aware that although the message is suppressed, the data from the original message will be in the Content Export (CE). When the CE exports a suppressed message, the following information are returned:

• Suppressed Message Content -> the content of the suppressed message.\
• Suppressed Message Sent From -> user that sent the suppressed message.\
• Suppressed Message Timestamp -> date when the message was suppressed.

> #### 🚧 Restricted Endpoint
>
> * Users can suppress their own messages only.
> * Users with the Content Management role can suppress any messages.
> * OBO: Please note that the SUPPRESS\_MESSAGES permission is needed for Apps to call this endpoint via OBO.
> * Starting with SBE 20.16, Messages in External rooms can also be suppressed. Please note however that if the counterpart does not yet have SBE 20.16, the message will only be suppressed on your end.
>
> See [Bot Permissions](https://docs.developers.symphony.com/building-bots-on-symphony/configuration/bot-permissions) for a list of roles and associated privileges.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rest-api.symphony.com/main/messages/suppress-message.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.