Webhook Logs

Introduction

The Webhook Logs section provides a comprehensive audit trail of all webhook activity in your system. Monitor webhook deliveries, troubleshoot integration issues, and track the success rate of your automated data transfers. This real-time log helps ensure your integrations are functioning properly and provides detailed information for debugging failed deliveries.

Accessing Webhook Logs

1. Log in to your Admin portal
2. Navigate to Settings → Webhook Logs in the left navigation sidebar
3. The Webhook Logs dashboard will display a chronological list of all webhook executions

Webhook Logs Dashboard

Main View

The Webhook Logs table displays detailed information for each webhook execution:

• Event - The specific action that triggered the webhook (e.g., order_created, order_updated)
• Object - The system resource type and identifier (e.g., Commerce::Order #3194935)
• Status - Visual indicator showing delivery success or failure
• Response Code - HTTP response code returned by the destination endpoint
• Created At - Exact timestamp when the webhook was triggered
• Actions - Additional options for viewing details or retrying failed deliveries

Status Indicators

• Failed Badge (Red) - Webhook delivery failed and may need attention
• Success Indicator - Webhook delivered successfully (shown as "Failed" count of 0)
• Response Code Colors - Visual cues help quickly identify successful vs problematic deliveries

Understanding Response Codes

Success Codes (200-299)

• 200 OK - Webhook received and processed successfully
• 201 Created - Webhook resulted in resource creation at destination
• 202 Accepted - Webhook accepted for processing (async handling)
• 204 No Content - Webhook processed with no response body needed

Client Error Codes (400-499)

• 400 Bad Request - Malformed webhook payload or invalid data
• 401 Unauthorized - Authentication credentials missing or invalid
• 403 Forbidden - Valid credentials but insufficient permissions
• 404 Not Found - Webhook endpoint URL no longer exists
• 429 Too Many Requests - Rate limiting in effect at destination

Server Error Codes (500-599)

• 500 Internal Server Error - Destination server encountered an error
• 502 Bad Gateway - Proxy or gateway issue at destination
• 503 Service Unavailable - Destination temporarily offline
• 504 Gateway Timeout - Request took too long to process

Using Webhook Logs

Monitoring Integration Health

1. Regular Review - Check logs daily for any failed deliveries
2. Success Rate - Calculate percentage of successful vs failed webhooks
3. Pattern Recognition - Identify recurring failures for specific events or endpoints
4. Performance Tracking - Monitor response times through timestamp analysis

Troubleshooting Failed Webhooks

1. Identify the Failure
   • Locate red "Failed" badges in the status column
   • Note the response code to understand the type of failure
   • Check the timestamp to determine when the issue occurred
2. Analyze the Pattern
   • Are failures isolated to specific events?
   • Do failures occur at certain times?
   • Is one endpoint failing while others succeed?
3. Common Solutions
   • 401/403 Errors - Update webhook authentication credentials
   • 404 Errors - Verify and update the webhook destination URL
   • 500 Errors - Contact the external service provider
   • Timeout Errors - Check endpoint performance and availability