Skip to main content
Webhooks are how Xobito knows that a customer just messaged you, a delivery receipt came back, or a template was approved. This page explains what they are, how Xobito sets them up automatically, and how to confirm they’re working.
The short version: you don’t have to do anything. Xobito configures the Meta → Xobito webhook for you during Connect Meta Business. This page is for when you want to verify it or troubleshoot.

​
What’s a webhook, in plain English?

A webhook is a URL that one system calls when something happens, so another system hears about it in real time — no polling, no delays. In your case, Meta needs to tell Xobito:
  • “A new message just came in for your number.”
  • “That message you sent was delivered.”
  • “It was read.”
  • “Your template was just approved by our review team.”
  • “Your phone number’s quality rating changed.”
Meta does this by sending a small HTTP POST request to a URL Xobito registered during connection. The URL is something like: 
https://dash.xobito.com/api/webhooks/whatsapp/{your-workspace-id}
Each request carries a JSON payload describing what happened.
This is the inbound direction only — Meta → Xobito. It has nothing to do with any “outbound webhooks” you may later configure from Xobito to your own systems. Those are documented in the Developer section.

​
Why it’s automatic

Traditionally, configuring webhooks meant copy-pasting a callback URL and a verify token into Meta Business Manager, choosing which events to subscribe to, and hoping you matched it all correctly. Xobito eliminates all of that. During the embedded signup:
  1. You click Login with Facebook and approve permissions.
  2. Meta issues Xobito an access token.
  3. Xobito uses that token to register our webhook URL and subscribe your WABA to the events we need: messages, statuses, templates, phone numbers.
  4. Meta starts delivering events immediately.
If you ever need to see or re-confirm the webhook, go to Setup → Account, click the connected WABA row, and look at the Webhook section.

​
The events Xobito subscribes to

Xobito listens for these Meta event fields:
Event fieldWhat it tells us
messagesA new inbound message from a customer.
message_template_status_updateYour template was approved, rejected, or paused.
message_template_quality_updateMeta adjusted the quality of a specific template.
phone_number_quality_updateYour number’s Green/Yellow/Red rating changed.
phone_number_name_updateYour display name was approved or rejected.
account_updateWABA-level status changes.
account_review_updateResults of an account review.
business_capability_updateMessaging tier or other capability changed.
When any of these fire, Xobito updates your UI, triggers notifications, and runs any matching automations.

​
Verify the webhook is working

To verify the incoming webhook is wired: send yourself a WhatsApp message from a phone the workspace doesn’t know — within 2–5 seconds the conversation should appear in the Live Inbox. If it doesn’t, see Troubleshooting.
If the inbound message lands in the Live Inbox, your webhook is healthy.

​
When the webhook breaks

Webhooks almost never “break” — but a few scenarios can interrupt them:

You revoked Xobito's permissions in Meta

If you removed Xobito from your Business Manager, the webhook stops. Fix: reconnect via Setup → Connect WhatsApp.

Your Meta access token expired

Rare, but possible for long-idle accounts. Fix: reconnect.

Meta platform outage

Every few months Meta has a short incident. No fix needed — events resume once Meta is back. They retry failed deliveries automatically.

Xobito webhook endpoint unreachable

Extremely rare. Our platform is monitored 24/7. If it happens, Meta retries for up to 7 days.

​
How Xobito detects a broken webhook

If your WABA has been silent for an unusually long time and Xobito expects messages to be flowing, the Account page will surface a warning banner.
You never need to “keep checking” — Xobito will surface any webhook issue directly in Setup → Account and by email to your workspace admins.

​
Re-establish the webhook

If the banner is showing, or you just want to re-register to be safe, run the Connect Meta Business flow again — this re-issues the access token and re-subscribes your WABA to the required events.
If reconnecting fails with an authorization error, your Meta access token is no longer valid. Run Connect Meta Business again to get a fresh token.

​
Can I use my own webhook URL instead?

No — the Meta → Xobito webhook must point at Xobito. If it pointed somewhere else, Xobito couldn’t show you inbound messages or track campaign delivery. What you can do is configure outbound webhooks from Xobito to your own systems. Those forward relevant events from Xobito to any URL you specify — great for syncing WhatsApp conversations into your CRM, helpdesk, or data warehouse. See Developer → Webhooks.

​
Security of inbound webhooks

Every event Meta sends to Xobito is:
Signed with an HMAC signature that Xobito verifies using a shared secret.
Delivered over HTTPS — events never travel in the clear.
Matched to your workspace via the unique webhook URL path.
If Meta ever sends an event whose signature doesn’t match, Xobito drops it silently — a malicious party can’t forge events into your inbox.

​
Troubleshooting

Classic webhook issue. Go to Setup → Account, look for a warning banner, and reconnect via Connect Meta Business. If the problem persists after reconnecting, contact support.
The most common cause is a partial or interrupted connect flow. Fix: disconnect and reconnect. Go to Setup → Account, click Disconnect, then run Connect WhatsApp again. See Disconnect for what that resets.
Usually a transient Meta error. Wait 5 minutes, then re-run Connect Meta Business. If it still fails, capture the error text and contact support.
Send a WhatsApp message to your connected business number from a personal phone (or a colleague’s) that isn’t already in your contact list. The new conversation should appear in the Live Inbox within a few seconds — that confirms inbound delivery is healthy.
Very rarely. Meta retries failed deliveries for up to 7 days, and Xobito acknowledges every successful receipt. If we ever do miss an event (e.g. our servers were briefly offline), Meta’s retry queue delivers it when we’re back.
Meta occasionally introduces new event types. If you see one that’s labeled “unhandled” in the log, it’s a Meta event Xobito hasn’t mapped yet — it doesn’t indicate a problem with your account.

​
Where to go next

Phone numbers

Manage display name, quality, and messaging tier.

Developer webhooks

Push Xobito events to your own systems.

Disconnect a WABA

Cleanly unlink your account and understand what happens to data.