> For the complete documentation index, see [llms.txt](https://support.whapi.cloud/help-desk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.whapi.cloud/help-desk/communities/send-comment-to-whatsapp-community-announcement.md).

# Send comment to WhatsApp community announcement

How to reply to announcements

Whapi.Cloud allows you to add a comment to an existing announcement in a WhatsApp Community.

A comment is linked to a specific [announcement message](/help-desk/communities/send-announcement.md), so you need its Message ID before sending the request.

### Send a comment

Use the following endpoint:

`POST https://gate.whapi.cloud/messages/{MessageID}/comment`

Replace `{MessageID}` with the ID of the Community announcement you want to comment on. You can retrieve the announcement ID, for example, using the [Get messages](https://whapi.readme.io/reference/getmessages) or [Get messages by chat ID](https://whapi.readme.io/reference/getmessagesbychatid) request (by specifying the announcement group ID instead of the chat ID). 

Check out [the article to learn how to find the announcement group ID](/help-desk/communities/introduction.md#how-to-find-the-correct-announcements-group).

#### Example request

```bash
curl -X POST "https://gate.whapi.cloud/messages/A7mK2pQ9vD4xR6tN8sF1cH5jL3wB0eY/comment" \
  -H "Authorization: Bearer <CHANNEL_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "body": "Thank you for the update. We will review the details."
  }'
```

#### Path parameter

* `MessageID` — the ID of the Community announcement to which the comment will be added.

#### Request body

* `body` — the text of the comment. It must be a non-empty string.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.whapi.cloud/help-desk/communities/send-comment-to-whatsapp-community-announcement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.