> 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/receiving/webhooks/incoming-webhooks-format/sent-message.md).

# Sent message

You can find more details about all parameters and their types in [the WebHook documentation](https://app.swaggerhub.com/apis-docs/HELLO_137/Whapi-Cloud-WhatsApp-API/1.8.5#/WebhookPayload).

Use the `messages.post` setting to get this webhook.

### Outgoing message from Mobile

```
{
  "messages": [
    {
      "id": "YhNqCveDWW90_t8lzrW25w-wO4Twl0rVw",
      "from_me": true,
      "type": "text",
      "chat_id": "919984351847@s.whatsapp.net",
      "timestamp": 1712995377,
      "source": "mobile",
      "status": "sent",
      "text": {
        "body": "Hey bro"
      },
      "from": "61371989950",
      "from_name": "Jonathan"
    }
  ],
  "event": {
    "type": "messages",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
```

***

### Outgoing from API

<pre><code>{
  "messages": [
    {
      "id": "yqJRppZk7BI-wNoTwl0rVw",
      "from_me": true,
      "type": "text",
      "chat_id": "919984351847@s.whatsapp.net",
      "timestamp": 1712995598,
      "source": "api",
      "device_id": 11,
      <a data-footnote-ref href="#user-content-fn-1">"status": "pending"</a>,
      "text": {
        "body": "Hello, this message was sent via API!"
      },
      "from": "61371989950"
    }
  ],
  "event": {
    "type": "messages",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
</code></pre>

{% hint style="info" %}

### Why Do I See `"status": "pending"` After Sending a Message?

When you send a message through the API, the initial response may include `"status": "pending"`.\
This is expected behavior — at the moment the request is processed, the API does not yet know the final delivery status.

You can interpret `"pending"` as “message sent, awaiting confirmation.”

To track delivery progress, use the webhook event **`statuses.post`**. This will notify you as soon as the message is delivered or read.\
You can also poll for status updates using the **GET message** endpoint.

> If the status remains `"pending"` and doesn’t change over time, it usually means:
>
> * The message format or content may be invalid
> * Your account may not have permission to send this type of message

If you're seeing persistent `"pending"` statuses, contact our support team — we’ll help you identify the issue and resolve it.
{% endhint %}

***

The messages statuses array contains all statuses that were sent to the webhook URL. Sent on event "`statuses.post`" or "`statuses.put`".  We mentioned more about the events here:[Detailed webhook settings](/help-desk/receiving/webhooks/detailed-webhook-settings.md#mode-setting)

### Status Sent

```
{
  "statuses": [
    {
      "id": "YhNqCveDWW90_t8lzrW25w-wO4Twl0rVw",
      "code": 2,
      "status": "sent",
      "recipient_id": "919984351847@s.whatsapp.net",
      "timestamp": "1712995378"
    }
  ],
  "event": {
    "type": "statuses",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
```

***

### Status Delivered

```
{
  "statuses": [
    {
      "id": "YhNqCveDWW90_t8lzrW25w-wO4Twl0rVw",
      "code": 3,
      "status": "delivered",
      "recipient_id": "919984351847@s.whatsapp.net",
      "timestamp": "1712995378"
    }
  ],
  "event": {
    "type": "statuses",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
```

***

### Status Read

```
{
  "statuses": [
    {
      "id": "YhNqCveDWW90_t8lzrW25w-wO4Twl0rVw",
      "code": 4,
      "status": "read",
      "recipient_id": "919984351847@s.whatsapp.net",
      "timestamp": "1712995581"
    }
  ],
  "event": {
    "type": "statuses",
    "event": "post"
  },
  "channel_id": "MANTIS-M72HC"
}
```

***

### Format

<table data-header-hidden><thead><tr><th width="154"></th><th></th></tr></thead><tbody><tr><td>id*</td><td><p><code>string</code></p><p>Message ID from event</p></td></tr><tr><td>code*</td><td><p><code>number</code></p><p>Status code</p></td></tr><tr><td>status*</td><td><p>StatusEnumstring<br>x-enum-descriptions: List [ "Message failed to send (Red error triangle in WhatsApp Mobile)", "Message pending to send (One clock in WhatsApp Mobile)", "Message received by WhatsApp server (One checkmark in WhatsApp Mobile)", "Message delivered to recipient (Two checkmarks in WhatsApp Mobile)", "Message read by recipient (Two blue checkmarks in WhatsApp Mobile)", "Voice-message played by recipient (Two blue checkmarks in WhatsApp Mobile)", "Message deleted by the user" ]</p><p>Message ack status</p><p>Enum:<br>[ failed, pending, sent, delivered, read, played, deleted ]</p></td></tr><tr><td>recipient_id</td><td><p>ChatID <code>string</code><br>pattern: ^[\d-]{10,31}@[\w\.]{1,}$</p><p>Chat ID</p></td></tr><tr><td>viewer_id</td><td><p>ContactID <code>string</code><br>pattern: ^([\d]{7,15})?$</p><p>Contact ID</p></td></tr><tr><td>timestamp*</td><td><p><code>string</code></p><p>Timestamp of the status message</p></td></tr></tbody></table>

[^1]: We have disclosed the reasons and description of this status below


---

# 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 dynamically by asking a question.

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

```
GET https://support.whapi.cloud/help-desk/receiving/webhooks/incoming-webhooks-format/sent-message.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
