{"id":766,"date":"2026-10-29T13:24:37","date_gmt":"2026-10-29T13:24:37","guid":{"rendered":"https:\/\/vectalk.com.br\/blog\/whatsapp-api-message-not-delivered\/"},"modified":"2026-10-29T13:24:48","modified_gmt":"2026-10-29T13:24:48","slug":"whatsapp-api-message-not-delivered","status":"publish","type":"post","link":"https:\/\/vectalk.com.br\/blog\/en\/whatsapp-api-message-not-delivered\/","title":{"rendered":"WhatsApp API message sent but not delivered: a troubleshooting checklist"},"content":{"rendered":"\n

Updated on October 29, 2026<\/em><\/p>\n\n\n\n

When the WhatsApp Business API accepts a message but it never arrives, the answer is in the status webhook: either the message is stuck at sent<\/code> (it left Meta’s servers but never reached the device) or it ended as failed<\/code> with an error code. In the first case, the usual causes are a customer who stayed offline, a customer who blocked your number, or a restricted country; in the second, the code tells you what happened and whether a retry makes sense. Meta only charges for delivered messages, so a message that never arrived is not billed.<\/p>\n\n\n\n

This checklist starts from the symptom you see in your system and ends with an action. For the full code reference, see our guide to WhatsApp API error codes<\/a>.<\/p>\n\n\n\n

Step 1: confirm the API accepted the message<\/h2>\n\n\n\n

Before talking about delivery, check the synchronous response from the send call. If it returned an error<\/code> object, the message never left: the problem is the token, a parameter, the template or a rate limit, not delivery. If it returned 200<\/code> with a wamid<\/code>, the message was accepted:<\/p>\n\n\n\n

{\n  \"messaging_product\": \"whatsapp\",\n  \"contacts\": [{ \"input\": \"5511999999999\", \"wa_id\": \"5511999999999\" }],\n  \"messages\": [{ \"id\": \"wamid.HBgLNTUxMTk5OTk5OTk5...\" }]\n}<\/code><\/pre>\n\n\n\n
Store that wamid<\/code>. It is how you match each status event to the original message. Without it in your database, troubleshooting becomes guesswork.<\/p>\n\n\n\n
Step 2: read the status in the webhook<\/h2>\n\n\n\n
From here on, everything arrives through the messages<\/code> webhook, in the statuses<\/code> array. Meta’s status webhook reference<\/a> defines five values:<\/p>\n\n\n\n
Status<\/th>What Meta says<\/th>What it means for troubleshooting<\/th><\/tr><\/thead>
sent<\/code><\/td>The message left Meta’s servers<\/td>Accepted and dispatched, but not on the device yet<\/td><\/tr>
delivered<\/code><\/td>Delivered to the user’s device<\/td>It arrived; from here it is billable<\/td><\/tr>
read<\/code><\/td>Displayed in an open chat on the device<\/td>Read (only counts as read if it was delivered)<\/td><\/tr>
played<\/code><\/td>First playback of a voice message<\/td>Voice messages only<\/td><\/tr>
failed<\/code><\/td>Failed to send or deliver<\/td>Check the errors<\/code> array<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
Two details prevent false alarms. First, if the user reads the message right away, Meta may skip the delivered<\/code> webhook, because read<\/code> already implies delivery. So “no delivered event” does not mean “not delivered” when there is a read<\/code>. Second, if no webhooks arrive at all, you have a different problem: review the setup in our guide to WhatsApp API webhooks<\/a> before blaming delivery.<\/p>\n\n\n\n
Our article on message status via webhook<\/a> shows how to store these events. Here we focus on what to do when they reveal a problem.<\/p>\n\n\n\n
Step 3: message stuck at sent<\/code><\/h2>\n\n\n\n
This is the most confusing case: no error, but no delivered<\/code> either. Meta’s Cloud API support page<\/a> lists the common causes:<\/p>\n\n\n\n