Webhooks — What and Why

A webhook is an HTTP endpoint on your server that Meta calls with a JSON payload whenever something happens on WhatsApp — an incoming message, a delivery or read receipt, a template approval or rejection. Unlike the API (where you call Meta), webhooks are Meta calling you.

Customer sends "Hello"
       ↓
Meta's servers receive it
       ↓
Meta POSTs JSON to your webhook URL
       ↓
Your server receives the payload
       ↓
Your code decides what to do (reply, log, trigger bot, etc.)

The difference between the API and webhooks#

What webhooks notify you about#

Incoming message from a customer:

{
  "messages": [{
    "from": "919959623255",
    "type": "text",
    "text": { "body": "Hello" }
  }]
}

Message delivered / read / failed:

{ "statuses": [{ "status": "delivered" }] }
{ "statuses": [{ "status": "read" }] }
{ "statuses": [{ "status": "failed" }] }

What your server can do with the data#

Your server receives the JSON and can choose to:

• Show the message on a dashboard
• Save it to a database (MySQL, Google Sheets, Airtable)
• Forward it to an automation tool (n8n, Zapier)
• Trigger an AI bot to generate a reply
• Send an automatic response back via the API

Setting up a webhook#

You need an HTTPS endpoint at a public URL, e.g. https://yourdomain.com/webhook. Register this URL in Meta's App Dashboard under WhatsApp → Configuration → Webhook. Meta will verify the endpoint with a GET request before activating it.

Frequently asked#

Gotchas & common mistakes#