What events do webhooks deliver?

Inbound messages (text, media, location, contacts), message status updates (sent, delivered, read, failed), and account-level events (phone number changes, quality rating updates).

How do I test webhooks locally?

Use Meta's webhook testing tool in Business Manager, or use a tunneling service like ngrok to expose your local server. With Convoup, you skip this entirely — webhooks are pre-configured.

Resources/WhatsApp API Webhooks

WhatsApp API Webhooks

How WhatsApp webhooks work, what events they deliver, and how to handle inbound messages and status updates.

Last reviewed: September 2, 2026•Reviewed by: Convoup Platform & Technical Operations

WhatsApp webhooks are HTTP callbacks that Meta sends to your server (or platform) when events occur — inbound messages, delivery confirmations, read receipts, and status changes.

Why This Matters

The Problem

The WhatsApp Business API is pull-based for sending (you call the API) but push-based for receiving. Without webhooks, you have no way to know when a customer sends a message, when your message is delivered, or when it is read.

Deep Dive

What WhatsApp API Webhooks Actually Is

When you configure a webhook URL in Meta Business Manager, Meta sends HTTP POST requests to that URL whenever a conversation event occurs. The payload is JSON and includes: the message content (text, image, document, etc.), the sender's phone number, a timestamp, and a conversation ID. Status webhooks tell you when a message is sent, delivered, and read. Platforms like Convoup handle webhook processing for you — you do not need to build your own webhook server.

In Practice

Real-World Examples

A customer sends "Where is my order?" — your webhook receives the message, and Convoup routes it to the appropriate agent queue.

You send an order confirmation template — a status webhook confirms delivery, which Convoup displays as a green checkmark in the thread.

Watch Out

Common Mistakes

Not validating webhook signatures — always verify that incoming webhooks are from Meta using the X-Hub-Signature header.

Building webhook handling from scratch when a platform like Convoup already does it.

Not handling webhook retries — Meta may resend webhook events if your endpoint does not respond with a 200 status.

From Our Experience

Expert Note

Convoup processes all WhatsApp webhooks automatically. When a message arrives, it appears in your shared inbox within seconds. Delivery and read receipts are shown per message. You never need to configure or manage webhook endpoints yourself.

Ready to implement what you learned?

See how Convoup handles this →

Frequently Asked Questions about WhatsApp API Webhooks

Keep Learning

Related Guides

WhatsApp Business API

What the WhatsApp Business API is, how it works, who it is for, and how to get started with the official Cloud API.

WhatsApp Cloud API

How the WhatsApp Cloud API works, its advantages over On-Premises, and how to get started without managing servers.

WhatsApp API Security

How WhatsApp API security works, what Meta handles, and what you are responsible for.

Convoup is built on the official WhatsApp Business Platform (Cloud API). Convoup is not endorsed by, affiliated with, or an official partner of Meta. WhatsApp is a trademark of its respective owner. Meta conversation charges apply separately from Convoup's subscription.

Built on WhatsApp Business Platform