WhatsApp Cloud API Webhook Verified but No Messages? Here’s the Fix
Lukas Becker
A customer writes to your WhatsApp business number at lunch. Nothing new appears in WordPress. In the Meta App Dashboard, the webhook still shows as verified. A green badge and an empty inbox are a common Cloud API surprise.
The badge and a live chat are not the same test. Saving the callback URL only checks that Meta can reach the address with a verification request. The conversation is delivered later, in a different request. Stop at the badge, and you can spend hours changing WordPress settings while the message was never sent to your app.
The walk-through below is for that situation: verification already succeeded, and real chats still do not show up. Work it in order, and leave firewalls and signature checks turned on.
The green check only tested a GET request
When you click Verify and Save, Meta asks your callback URL a short question. The request is a GET, and it includes hub.mode, hub.challenge and hub.verify_token. Your endpoint compares the verify token with the string you typed in the dashboard, then returns the challenge value. If that answer is correct, the dashboard marks the webhook as verified.
Incoming chats do not use that GET request. Meta later posts a JSON payload to the same URL. Status changes for messages you already sent travel on that POST as well, on the messages field. A site can pass the handshake and still miss every conversation if the POST is never sent, never accepted, or quietly discarded.
Verification only confirms the address. You still have to make sure this app is allowed to receive that account’s events, that the URL is public HTTPS, and that the person writing to you is allowed to use this test or live number.
First fork: did a POST reach the site?
Before you change any Meta settings, send one test chat, note the time (and its time zone), and search for a POST to the exact callback path in the web-server log, the host’s request log, or the receiving plugin’s log. Opening the callback URL in a browser is a GET, and it is not a WhatsApp delivery.
Either no POST was recorded, or a POST arrived, and WordPress still did not create a conversation. Those problems have different fixes. Guessing between them leads people to rewrite plugin code when the app was never subscribed, or to resubscribe an account when a signature check is already rejecting the payload.
When the server never saw the POST
The app is missing from the WhatsApp account’s subscription list
Turning on webhook fields in the App Dashboard is only half of the hookup. Meta still expects the app to be subscribed to each WhatsApp Business Account whose events you want, with POST /{WABA_ID}/subscribed_apps. Teams miss this after they add a second number, clone an app, or treat Verify and Save as the last step.
Use a current Graph API version and an access token that can manage that WABA:
curl -X POST "https://graph.facebook.com/<API_VERSION>/<WABA_ID>/subscribed_apps" \
-H "Authorization: Bearer <ACCESS_TOKEN>"
You should see {"success": true}. Then list the subscribers and look for your app’s name and ID:
curl -X GET "https://graph.facebook.com/<API_VERSION>/<WABA_ID>/subscribed_apps" \
-H "Authorization: Bearer <ACCESS_TOKEN>"
If your app is not in that list, Meta will not deliver that account’s message events to it. Subscribe every WABA you actually use, and check that a recently retired app did not replace this one.
The messages field is off, or events are going to another URL
Open the WhatsApp webhook settings and confirm the messages field is selected. That is the field that carries both customer replies and the delivery status of your own messages. The dashboard can also send a sample payload. A sample that arrives only proves this URL can accept a test body. It does not prove that a real chat on this WABA will be routed to the same app.
Also compare the saved callback with the URL your plugin documents, including HTTPS and the path. An old staging host, a typo, or a phone-number-level override can send live events somewhere else while the dashboard still shows a verified address.
You tested with the wrong number, or the app is still in Development mode
Meta’s Getting Started flow gives you a test business number. That number is for a short, verified recipient list—in practice, up to five phone numbers you add and confirm—not for ordinary customers. If you write from a personal WhatsApp account that was never added to that list, or you write to a production number while the app is still in Development mode, the dashboard sample can succeed, and the real chat can go nowhere you are watching.
Match the business number the customer wrote to, the number you sent from, and the app’s mode. For real customers, use a production number on a live app, with the permissions Meta requires. Until then, test only from a recipient you have verified.
The request never reached a public WordPress site
Meta has to post to a public HTTPS URL. It cannot deliver to localhost. If the site only exists on your laptop, point Meta at a public HTTPS tunnel first. That setup is covered in this localhost webhook guide.
On a live host, a CDN, firewall or security plugin can also swallow the POST. Verification can still pass because it is a GET with query parameters, while the message is a POST with a JSON body. If a security log shows a 403 or a blocked rule at the same moment, follow how to find and fix a WordPress webhook 403 and keep the exception narrow.
When a POST arrived, but the inbox stayed empty
If the access log already shows Meta’s POST, stop hunting for subscription problems and look at what your site did with the body.
- The signature check used the wrong bytes. Event notifications include an
X-Hub-Signature-256header. Your code should hash the raw request body with the app secret, then compare that result with the value aftersha256=. If you parse the JSON first and hash a rebuilt string, the check can fail on every real event. Leave the check enabled. - The endpoint was too slow, or it did not return 200. Acknowledge the POST quickly, then finish the work in the background where you can. A long PHP request, a timeout, or a 4xx/5xx response looks like a failed delivery. Meta will retry for a while, and a sloppy handler can create the same conversation twice. After retries stop, there is no official way to download the missed payload, so you cannot plan on a later backfill.
- The payload was a status update, not a new inbound chat. The
messagesfield can describe deliveries and reads as well as a customer’s text. If your code only stores one shape and ignores the other, the log will show activity while the inbox still looks empty. Read the raw body once before you decide nothing arrived.
If outbound sends work and inbound chats do not, return to the subscription list, the messages field, and the test-recipient list. If both directions failed after a day of working, the credential used by the plugin may have lapsed. That is a different problem; see how to create a System User access token.
A compact runbook
| What you saw | Do this next |
|---|---|
| Verified badge, no POST in the logs | List subscribed apps, confirm the messages field, check the callback URL, then Development mode and the test recipient list |
| Dashboard sample arrives; a real chat does not | Compare the test number with the live number, and confirm who is allowed to write to it |
| POST is in the log; inbox is still empty | Inspect the raw body, the signature check, and the HTTP status your site returned |
| Security log shows a block or 403 on the POST | Use the webhook 403 guide and change only the matching rule |
| Sends worked yesterday and fail today | Replace a short-lived token; do not redo the whole webhook unless the URL also changed |
Once events really reach WordPress, you still need a place in wp-admin to read and answer them. Kinetix Messaging is a free plugin that puts WhatsApp beside Messenger, Instagram DM, Telegram, and the site’s live chat in one inbox. It does not skip the subscription and logging checks in this article. If you are comparing an inbox with a chat button, the multi-channel inbox overview is a useful next read, and WhatsApp Business App vs Cloud API explains when the API is the right product in the first place.
Frequently asked questions
I can send WhatsApp messages from WordPress, but I never see replies. What should I check first?
Outbound sending and inbound webhooks use different paths. A working send only proves the access token and phone number ID can call the API. Replies still depend on the WABA subscription, the messages field, and a POST that your site accepts.
Do I have to click Verify and Save again after I subscribe the WhatsApp account?
Not if the callback URL and verify token are unchanged and the dashboard still shows the endpoint as verified. Subscribing the WABA is a separate API step. Recheck verification only if you changed the URL, the token string, or the server that answers the GET.
Why did chats work on the test number and stop when I added my real business number?
The new number belongs to a WABA that must be subscribed of its own, and the app often needs to be live before real customers can use it. Recipients you verified for the test number do not automatically cover a production line. Repeat the subscription check for the account that owns the new number.
If I missed a customer message this morning, can I download that webhook later?
No official endpoint gives you the missed payload after retries have finished. Repair the cause, then ask someone to write again or send a new test chat and watch the logs as it happens.