# Get a message

`GET /api/reporting/v1/messages/{id}`  (operationId: `getMessage`, group: Reporting)

One message by its WhatsApp message id (wamid), with its current delivery status and, for a failed send, the reason.

Part of the full API, which is included in the Scale plan. Any one of these scopes is enough: `inbox`, `contacts`, `inbox:read`, `contacts:read`. Chat content: messages, names and phone numbers.

**Parameters**

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `id` | path | string | yes | WhatsApp message id. |

**Response 200**: OK (schema `MessageDetail`)

Example:

```json
{
  "id": 1044,
  "message_id": "wamid.HBgM...A1",
  "sent_at": "2026-10-02T09:05:12.000Z",
  "sender_type": "agent",
  "actor": {
    "user_id": 41,
    "name": "Anita"
  },
  "sender_label": "Anita",
  "type": "text",
  "text": "We are looking into it.",
  "template_name": null,
  "media_url": null,
  "status": "read",
  "source": "whatsapp",
  "phone": "919876543210",
  "error": null
}
```

**Errors specific to this call.** The common ones (401, 403, 429 and the rest) are in the [Errors guide](https://inboxwa.online/docs/api/guide/errors.md).

| Status | error | When |
| --- | --- | --- |
| 404 | `not_found` | No such message in this workspace. |

Part of the InboxWA API reference: https://inboxwa.online/docs/api . Full reference as one document: https://inboxwa.online/docs/api.md . OpenAPI: https://inboxwa.online/openapi.json