These endpoints are called by Meta, not by you. They exist so replies and delivery receipts reach MsgOrb.
| Endpoint | Purpose |
|---|---|
/api/webhooks/meta | Inbound messages, delivery and read receipts, Smart Auto-Replies, STOP handling |
/api/webhooks/whatsapp | Meta's subscription verification handshake |
Both accept GET for Meta's hub.challenge verification and POST for events. Incoming payloads are verified against your app secret before MsgOrb acts on them.
What to configure at Meta
In your Meta app under WhatsApp → Configuration, set the callback URL to your MsgOrb webhook endpoint, set the verify token to the value configured for your deployment, and subscribe to the messages field.
If Embedded Signup completed successfully, this is already configured for you.
What arrives because of them
- Inbound replies appear in the Inbox and as Received rows on Delivery and Queue Health.
- Delivery and read receipts move a message from Sent to Delivered to Read.
- A reply opens the 24-hour window for that number.
- STOP and its variants mark the contact Opted Out.
These are inbound endpoints only. There is no MsgOrb API for creating campaigns, groups, templates or contacts other than the two endpoints documented in this section.