Plugin Pros

Meta Webhook Verify Token: What It Is and Why “Verify and Save” Fails

Lukas Becker

Meta Verify and Save error next to a webhook verify token field.

You paste a callback URL, type a Meta webhook verify token, click Verify and Save, and Meta says the callback URL or verify token couldn’t be validated. The dashboard never turns green, and you won’t be able to subscribe to WhatsApp, Messenger, or Instagram events until that handshake works.

This post is about that first step failing. The verify token is not a password Meta issues, and “Verify and Save” is not a test of live chats. If the badge is already green and messages still never arrive, use WhatsApp Cloud API webhook verified but no messages instead.

What a Meta webhook verify token is

The verify token is a secret string you invent. You enter the same string in two places: your webhook endpoint (in WordPress, usually a plugin field) and the Verify Token field in the Meta App Dashboard.

Meta does not generate this value for you. There is nothing to “look up” in API Setup or Business Settings. A short, hard-to-guess phrase is enough, for example my_kmbp_whatsapp_token_2026. Write it down. The two copies must match exactly.

The same handshake is used across Meta products. In Kinetix Messaging, WhatsApp, Facebook Messenger, and Instagram DM each have a Verify Token field. The idea is the same; only the callback URL changes.

What happens when you click Verify and Save

Meta sends a GET request to your callback URL. Officially, that request includes three query parameters:

  • hub.mode — always subscribe for a verification request.
  • hub.verify_token — the string you typed in the dashboard.
  • hub.challenge — a number Meta expects you to send back.

A sample request looks like this:

GET https://www.your-domain.com/webhooks?
  hub.mode=subscribe&
  hub.challenge=1158201444&
  hub.verify_token=meatyhamhock

Your endpoint must confirm that hub.mode is subscribe, that hub.verify_token matches the secret you stored, and then respond with HTTP 200 and the raw hub.challenge value. If that answer is correct, the dashboard marks the webhook as verified.

Two details catch a lot of WordPress sites:

  • Meta wants the challenge itself, not a JSON object such as {"challenge":"1158201444"} and not an HTML page.
  • PHP converts dots in query names to underscores, so the parameter arrives as hub_verify_token and hub_challenge. A custom snippet that only reads hub.verify_token can reject a valid request.

This GET is only the handshake. Later, customer messages arrive as a POST with a JSON body and an X-Hub-Signature-256 header. Passing Verify and Save does not prove those POSTs will succeed.

Why Verify and Save fails (and the fix)

The verify tokens do not match

This is the most common cause, and the easiest to miss. A trailing space, a different capital letter, or an old token left in one of the two fields will fail the check. Copy the string from your plugin and paste it into Meta. Do not retype it from memory. Save the plugin settings first, or Meta will be compared against an empty or outdated value.

The callback URL is wrong

The URL in Meta must match the webhook URL your plugin shows, character for character: https, the hostname, and the path. Typical mistakes include http://, a missing or extra www, a staging domain, and a typo in the REST path. For WhatsApp in Kinetix, the documented URL looks like this:

https://yourdomain.com/wp-json/kmbp/v1/webhooks/whatsapp

Copy the URL from the plugin. Do not invent the path. Messenger and Instagram use their own callback URLs from the same settings screen. If permalinks are still set to Plain, the pretty /wp-json/... address may not resolve. Choose any other permalink structure, save, and try again.

The site is not public HTTPS, or the certificate is self-signed

Meta requires HTTPS with a valid TLS/SSL certificate. Self-signed certificates are not supported. A browser warning, an expired certificate, or a missing intermediate can make the GET fail even when the site opens for you.

You pointed Meta at localhost

localhost, 127.0.0.1, and local domains such as .test are not reachable from Meta’s servers, so the GET never arrives. For local testing, give the site a public HTTPS tunnel and paste that URL as the callback. See why WhatsApp webhooks fail on localhost.

A firewall, security plugin, or Cloudflare returns 403

The verification request is an unauthenticated GET from Meta’s servers. A WAF, host firewall, security plugin, or Cloudflare rule (including bot fight or country blocks) can reject it with 403 or a challenge page. Meta then treats the callback as invalid. Do not turn the firewall off. Find the request in the security log and add a narrow exception for the webhook path. If the status is 403, follow how to find and fix a WordPress webhook 403.

Caching or a redirect hides the challenge

Page caches and some CDNs cache GET requests. If the webhook URL is cached, Meta may receive a stored homepage, a 404, or an empty response instead of the challenge. Exclude that path from page caching. Redirects cause the same symptom: an HTTP-to-HTTPS hop, a www redirect, or a trailing-slash redirect can drop query parameters. Put the final HTTPS URL, the one that returns 200 with no redirect, in the Callback URL field.

The endpoint returns JSON, HTML, or a login page

If your code wraps the challenge in JSON, or WordPress returns a theme page, a maintenance screen, or a staging password prompt, the handshake fails. The body must be the challenge and nothing else. Opening the callback URL in a browser is not a fair test, because that visit does not send hub.mode, hub.verify_token, and hub.challenge.

A quick checklist

CauseWhat to checkFix
Token mismatch or whitespaceThe plugin field and Meta’s Verify TokenCopy and paste the same string, then save the plugin first
Wrong callback URLHTTPS, hostname, and the path from the pluginPaste the plugin’s webhook URL; fix Plain permalinks if needed
Certificate or HTTPBrowser padlock and certificate expiryUse a valid public certificate; Meta does not accept self-signed
Localhost or a private hostWhether Meta can reach the URL from the internetUse a public host or an HTTPS tunnel
403 or a block pageCDN, host, and security-plugin logs at the same momentAllow only the webhook path; see the 403 guide
Cached or redirected GETWhether the URL 302s or returns HTMLExclude the path from cache; use the final 200 URL
JSON or extra outputThe raw response bodyReturn only the hub.challenge value

How Kinetix Messaging handles the handshake

You do not have to write the GET handler yourself. In Kinetix Messaging, open Settings, choose WhatsApp, Messenger, or Instagram DM, and turn the channel on.

  1. Fill in the credentials for that channel, including the App Secret.
  2. In the Webhook Verify Token field, type any secret string you will remember. This is your Meta webhook verify token.
  3. Copy the webhook URL shown on the page. For WhatsApp it ends with /wp-json/kmbp/v1/webhooks/whatsapp.
  4. Click Save in the plugin so the token is stored before Meta calls your site.
  5. In the Meta App Dashboard, paste that URL as the Callback URL, paste the same verify token, and click Verify and Save.

When Meta’s GET arrives, the plugin checks the token and returns the challenge. A green “Verified” mark means the handshake succeeded. After that, subscribe to the message fields for that product (for WhatsApp, that includes messages). The full WhatsApp walk-through is in how to connect your WhatsApp channel in WordPress. If Verify and Save succeeds but the inbox stays empty, the problem has moved past the verify token. Use the verified-but-no-messages checklist before you change the token again.

Frequently asked questions

Where do I get a Meta webhook verify token?

You create it. Type a secret string into your plugin and into Meta’s Verify Token field. Meta does not issue this token in the App Dashboard or in an API response.

Does a failed Verify and Save mean my access token is wrong?

Usually no. The handshake uses the verify token and the callback URL, not the WhatsApp access token. A short-lived access token is a different credential. See how to create a System User access token if sends fail after a day.

Can I reuse the same verify token on WhatsApp, Messenger, and Instagram?

You can use the same string or a different one per channel, as long as the value in Meta matches the value stored for that channel’s endpoint. The callback URLs still have to be the ones the plugin shows.

I verified the webhook yesterday and it failed again today. Why?

Something in the GET path changed: the callback URL, the stored token, SSL, a new firewall rule, or a cache covering the endpoint. If none of those changed and the dashboard still shows Verified, you do not need to click Verify and Save again to subscribe to events.

Get the handshake right, then use the inbox

Kinetix Messaging is a free WordPress plugin that stores your verify token, serves the callback URL, and puts WhatsApp, Messenger, Instagram, Telegram, and live chat in one inbox after the webhook is verified. Start with the token check above, then see the multi-channel inbox setup.

Official documentation