Webhook Logs
The Webhook Logs section provides complete visibility into all webhook events triggered from your MSG91 account to your configured webhook URL across services.
This feature helps you to:
Verify whether event callbacks are reaching your server
Debug webhook failures
Inspect the exact payload sent by MSG91
Check the response returned by your server
Webhook Logs are essential while setting up or troubleshooting any webhook configuration in MSG91.
Where to Find Webhook Logs
In the MSG91 dashboard, Webhook Logs are available inside every service.
Each service maintains its own webhook activity logs for easier tracking and debugging.
Steps to access:
Open the specific service you are using (e.g., WhatsApp, SMS, Voice, RCS, SendOTP, Email).
From the left-side panel of that service, click on Webhook Logs.
.webp)
Filters Available
.webp)
You can filter webhook logs using:
Date Range Filter (top-right)
Filter logs for a specific time period to analyze webhook activity
Column | Description |
|---|---|
Date | Timestamp when the webhook was triggered |
Request Id | Unique ID of the event generated by MSG91 |
WebhookId | ID mapped to your webhook configuration |
Webhook Name | Name assigned to the webhook during setup |
Service | The MSG91 service from which the webhook originated (SMS, Email, Voice, WhatsApp, etc.) |
Status | Shows whether the webhook was Sent or Failed |
Failure Reason | Displays error message if delivery failed |
Snapshot (<> icon) | View complete request & response payload |
Status Meaning
Sent
Webhook was successfully delivered to your server
Your server accepted the request
No issue from MSG91’s delivery side
You can open Snapshot to verify the HTTP response code returned by your server.
Failed
Webhook could not be delivered. The Failure Reason column will show the exact cause.
Common reasons:
Invalid webhook URL
Server unreachable
SSL/HTTPS issues
Timeout from your server
Server returned non-200 HTTP status
Using the Snapshot Option
Click the <> icon to see:
JSON payload sent by MSG91
Headers and request details
HTTP response returned by your server
This is especially useful for developers to debug webhook listener issues.
.webp)
Best Practices for Webhook Setup
To ensure successful webhook delivery:
Your endpoint must return HTTP 200
Response time should be under 5 seconds
Use a valid HTTPS (SSL secured) URL
Ensure your server/firewall is not blocking MSG91 requests
When to Use Webhook Logs
Use this section when:
You are not receiving event callbacks
You want to verify webhook activity
You are testing a new webhook URL
You need to debug webhook failures across any MSG91 service
Webhook Logs provide full transparency into webhook communication between MSG91 and your server, making troubleshooting fast and reliable across all services.