Skip to main content
PingBack exposes webhook endpoints that your connected channel providers call to deliver inbound messages. When a customer sends a message on WhatsApp, Instagram, Telegram, X, or email, the provider posts the event to the corresponding PingBack endpoint, and PingBack routes it into the right conversation automatically. These are inbound webhooks — the channel platforms call PingBack, not the other way around.
You configure these webhook URLs in your channel provider’s dashboard. Once you connect a channel in PingBack, the routing and processing happen automatically — you do not need to write any additional code.

​
Available webhook endpoints

​
Meta webhook verification (WhatsApp and Instagram)

When you register a webhook URL in the Meta App Dashboard, Meta sends a one-time GET request to verify that your endpoint is reachable. PingBack handles this automatically. Meta sends three query parameters: PingBack responds with the hub.challenge value when hub.verify_token matches pingback_verify. Use pingback_verify as your verify token when setting up the webhook in your Meta App.
1

Open your Meta App Dashboard

Go to developers.facebook.com, select your app, and navigate to WhatsApp → Configuration (or Instagram → Webhooks).
2

Enter the webhook URL

Set the callback URL to:
For Instagram, use:
3

Enter the verify token

Set Verify Token to:
4

Subscribe to message events

Select the messages field under Webhook Fields and click Verify and Save. Meta will call PingBack’s GET endpoint to confirm the token, then begin delivering events via POST.

​
Telegram and X setup

For Telegram and X, the webhook URL includes your channel ID. You can find your channel ID in PingBack under Settings → Channels after connecting the channel. Telegram example:
X example:
Register these URLs in your Telegram bot settings or X Developer Portal respectively. PingBack handles message parsing and routing once the webhook is active.

​
What happens after a webhook fires

When PingBack receives a webhook event, it:
  1. Identifies the channel and the customer who sent the message.
  2. Finds or creates a conversation for that customer.
  3. Saves the message and emits a new_message Socket.IO event to your connected agents in real time.
Your agents see the message appear immediately in the inbox without any additional setup. For more on connecting individual channels, see the Channels section.