> For the complete documentation index, see [llms.txt](https://docs.channel360.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.channel360.co.za/api-usage/receive-delivery-updates/check-a-notification-status.md).

# Check a notification's status

Look up one notification's current status, to fill a gap when a webhook went missing.

Look up where one template notification is now: pending, sent, delivered, read or failed.

{% hint style="warning" %}
**This is not the way to track your messages.** Use [webhooks](https://docs.channel360.co.za/api-usage/receive-delivery-updates.md) for that. Channel360 tells you about every change as it happens, and nothing has to ask.

Use this lookup only to fill a gap: a webhook your server missed, a message that seems stuck, or a status you want to double-check. Do not call it in a loop for every message you send.
{% endhint %}

## When to use it

| Situation                                                                     | What to do                                                           |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------- |
| Your server was down, and Channel360 stopped retrying after about 15 minutes. | Look up the notifications you sent during the outage.                |
| You never received a final update for a message.                              | Look it up once, then decide whether to resend.                      |
| A customer says they did not get a message.                                   | Look it up to see whether it was delivered, read or failed, and why. |

## Before you start

* **An API key** and **your organisation ID** — see [Authentication](https://docs.channel360.co.za/api-usage/get-started/authentication.md).
* **The notification `_id`** returned when you sent it. A successful send answers `201` with `{ "notification": { "_id": "6710f3c2a1b2c3d4e5f60789" } }`. Store this ID with your own record. The lookup does not accept your `msg_id`.

## Request

`GET` `/org/<ORG_ID>/notification/<NOTIFICATION_ID>`

```bash
curl "https://channel360.co.za/v1.1/org/<ORG_ID>/notification/<NOTIFICATION_ID>" \
  -H "Authorization: Bearer <API_KEY>"
```

| Path parameter    | Type   | Description                                                    |
| ----------------- | ------ | -------------------------------------------------------------- |
| `ORG_ID`          | string | Your organisation ID. Required.                                |
| `NOTIFICATION_ID` | string | The `_id` the send request returned (24 characters). Required. |

## Response

HTTP `200`:

```json
{
  "notification": {
    "_id": "6710f3c2a1b2c3d4e5f60789",
    "status": "FAILED",
    "msg_id": "order-88422",
    "templateName": "payment_confirmation",
    "failureReason": "Message undeliverable",
    "errorCode": "131026",
    "createdAt": "2026-10-27T09:14:02.511Z",
    "deliveredAt": null,
    "updatedAt": "2026-10-27T09:14:05.020Z"
  }
}
```

| Field           | Description                                                                 |
| --------------- | --------------------------------------------------------------------------- |
| `_id`           | The notification ID.                                                        |
| `status`        | Where the message is now. See [Statuses](#statuses).                        |
| `msg_id`        | Your own reference, exactly as you sent it. `null` if you did not send one. |
| `templateName`  | The template that was sent.                                                 |
| `failureReason` | Why it failed, when `status` is `FAILED`. Otherwise `null`.                 |
| `errorCode`     | WhatsApp's error code for the failure, when there is one. Otherwise `null`. |
| `createdAt`     | When Channel360 accepted the send.                                          |
| `deliveredAt`   | When the message reached the customer's phone. `null` until then.           |
| `updatedAt`     | When the status last changed.                                               |

A field with no value is `null`, never missing.

### Statuses

Each status matches the webhook event that would have told you about it.

| `status`               | Meaning                                                           | Webhook event                                                   |
| ---------------------- | ----------------------------------------------------------------- | --------------------------------------------------------------- |
| `PENDING`              | Channel360 has the message but has not handed it to WhatsApp yet. | —                                                               |
| `SUBMITTED`            | WhatsApp accepted the request. The message can still fail.        | —                                                               |
| `DELIVERED TO CHANNEL` | WhatsApp sent the message.                                        | `notification:delivery:channel`                                 |
| `DELIVERED`            | The message reached the customer's phone.                         | `notification:delivery:user`                                    |
| `READ`                 | The customer opened the message.                                  | `conversation:read`                                             |
| `FAILED`               | The message was not delivered. `failureReason` says why.          | `notification:delivery:failure` or `notification:match:failure` |

### What the lookup does not tell you

* **It shows the status now, not a history.** You see the latest status only. `updatedAt` is when it last changed. Your webhook events are the timeline.
* **`PENDING` and `SUBMITTED` are not final.** A message can sit in these for a short while before it moves on. Look again later rather than resending straight away, or you may send it twice.
* **It covers template notifications sent through the API.** Replies you send to a customer are not included.

## What can go wrong

| What you see                                 | Why                                                                                               | What to do                                                                     |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| **400** `id must be a valid notification id` | The ID is not a 24-character notification ID. You may have used your `msg_id` instead.            | Use the `_id` from the send response.                                          |
| **401 / 403** unauthorised                   | The API key is missing, wrong, or belongs to another organisation.                                | Check the `Authorization: Bearer …` header and the organisation ID.            |
| **404** `Not Found`                          | No notification with that ID in this organisation. This includes an ID from another organisation. | Check the ID and that the organisation ID in the URL is the one you sent from. |

## Next

{% content-ref url="/pages/NtsbXspiU4OagtOGfKyY" %}
[Receive delivery updates](https://docs.channel360.co.za/api-usage/receive-delivery-updates.md)
{% endcontent-ref %}
