The send API

Read a WhatsApp message's status through the API: delivered, read or failed

The reference for the message status address of ArabyBot's API: the seven statuses and what they mean, the response shape, a failed message and its reason, and the refusals.

4 min read Updated 16 November 2026 ArabyBot team
The ArabyBot teamOfficial Meta partner · written from our own platform data
On this page 8
  1. The address and authentication
  2. The fields
  3. An example request
  4. The response
  5. What we measured on this API
  6. The refusals
  7. The limits
  8. Frequently asked questions

The short answer

With a GET request to the messages address followed by the message id returned when you sent it. The response gives its status now: queued, accepted by WhatsApp, sent, delivered, read or failed; a failed message comes back with Meta's code and the reason. The message's first identifier stays the same even if the queue sent it again.

Also asked as: «اعرف ازاي ان رسالة الواتساب وصلت من الكود» · «حالة رسالة واتساب api» · «check whatsapp message delivery status api»

The address and authentication

GET https://app.arabybot.com/api/v1/messages/{id}

Send the send key in the header Authorization: Bearer abk_… or X-Api-Key. You create the key on the «Developer tools» page of the ArabyBot dashboard, and it is shown once when it is made. The call goes from your server, so never put the key in a page a visitor opens or in a mobile app.

The fields

  • id (required) The message id at the end of the address, the id field returned when you sent it.

An example request

cURL

curl https://app.arabybot.com/api/v1/messages/512 \
  -H "Authorization: Bearer abk_YOUR_KEY"

PHP

$ch = curl_init('https://app.arabybot.com/api/v1/messages/512');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['Authorization: Bearer abk_YOUR_KEY'],
]);
$answer = json_decode(curl_exec($ch), true);
$status = curl_getinfo($ch, CURLINFO_RESPONSE_CODE);
curl_close($ch);

Python

import requests

r = requests.get(
    'https://app.arabybot.com/api/v1/messages/512',
    headers={
        "Authorization": "Bearer abk_YOUR_KEY",
    },
    timeout=30,
)
print(r.status_code, r.json())

Node.js

// Node.js 18+
const r = await fetch('https://app.arabybot.com/api/v1/messages/512', {
  headers: {"Authorization": "Bearer abk_YOUR_KEY"},
});
console.log(r.status, await r.json());

The response

200
{ "success": true, "id": 512, "message_id": "wamid.…", "to": "966501234567",
  "status": "delivered", "reference": "order-1042-shipped",
  "created_at": "2026-11-16 18:04:10", "updated_at": "2026-11-16 18:04:13" }

# a failed message carries the reason
{ "success": true, "id": 513, "status": "failed",
  "error": { "meta_code": "131026", "message": "…", "meta_message": "…" } }
  • queued and sending: the message is in the queue or on its way to WhatsApp.
  • accepted: WhatsApp took it. sent, delivered and read: it was sent, then reached the customer's phone, then was read.
  • failed: it did not arrive, and Meta's reason is in error.
ArabyBot's API as it runs today, read from the system itselfmeasured 16 November 2026

What we measured on this API

62%of the templates were read
32%were delivered and not read yet
6%failed
ArabyBot's measurement on 11,900 templates sent through the send API between 18 Oct and 16 Nov 2026measured 16 November 2026

One account carries over 99% of these messages; so this is one business's result, not a market rate. The queue sent 224 messages again by itself after a temporary refusal. The most common failure reasons, as Meta returned them:

The refusals

Every refusal comes back as JSON with "success": false, an error_code, and a message in Arabic in message and in English in message_en:

  • 404 NOT_FOUND: No message with this id on this account.
  • 401 NO_KEY: The key was not sent in the header.
  • 401 INVALID_KEY: The key is wrong or was revoked; create one under «Developer tools».
  • 402 SUBSCRIPTION_EXPIRED: The account's subscription has ended.
  • 403 NOT_IN_PLAN: The account's plan does not include «Developer tools».
  • 429: The key passed 600 requests a minute; wait the time written in the Retry-After header.
  • 500 SERVER: A failure on our side; try again, and tell support if it repeats.

The limits

600 requests a minute per key. Whatever exceeds the pace WhatsApp accepts for your number waits in a queue, comes back with the status queued, then goes out by itself, so no message is lost. Meta's own limits on your number, how many people you may start conversations with in a day and the quality rating, stay as they are behind this API.

The full send API reference · All APIs for developers

Frequently asked questions

1

What is the difference between accepted and delivered?

accepted means WhatsApp took the message from us. delivered means it reached the customer's phone. A message can stay accepted if their phone is off.

2

Where do I find why a message failed?

In the error field of the response: it holds Meta's code in meta_code and the reason text. Our WhatsApp error-code pages explain each code and its fix.

The ArabyBot teamOfficial Meta business partner in the Middle East 264 guides Figures from our platform All guides

How we write these guides Figures come from our platform and Meta's actual invoices, dated with their sample; we describe what works today, not what we plan, and say what we do not do and when someone else is the better choice. Reviewed by the ArabyBot team on 16 November 2026.

Share this guide

Try the agent before you pay anything

The agent that will answer your customers is the one answering you now: ask it from the chat button here or on WhatsApp. Your account is free with no credit card, and the free trial on your own number or page is activated after you contact our team on customer-service WhatsApp.

And you run all of it from your phoneEverything on this page is also run from the ArabyBot mobile app — replies, orders, campaigns and AI reports. Not a web dashboard only.