Webhook Logs

Every webhook execution is logged, allowing you to monitor deliveries, troubleshoot failures, and correlate webhooks with the original API requests.

Viewing Webhook Logs

All Webhook Logs

Click Automation in the sidebar, then select Webhooks
Click Webhook Logs tab
View all webhook executions across all webhooks

Logs for a Specific Webhook

Click Automation in the sidebar, then select Webhooks
Click on a specific webhook
Select the Logs tab

Log Entry Details

Each log entry contains:

Field	Description
Webhook Name	The webhook that was triggered
Event Type	The event that triggered the webhook (e.g., `request.success`)
Executed At	Timestamp of the execution
Success	Whether the delivery succeeded
Response Status	HTTP status code from your endpoint
Response Time	How long the request took (ms)
Retry Count	Number of retry attempts
Request ID	Links to the original API request

Log Entry Detail View

Click on a log entry to see full details:

The delivery payload (the event data, the headers and body KnoxCall sent, and the response body your endpoint returned) can carry proxied request bodies and audit details, so it is treated like a request log’s captured payload: the detail opens with the payload withheld for everyone, and an Owner or Admin clicks Reveal payload to see it, with a fresh second factor each time and an audit entry written first (see Who can see a delivery’s payload). A log policy that withholds a request path’s payload also withholds the delivery for that path, and an audit.event delivery also needs permission to read audit details. Everyone sees the delivery’s status, timing, response code and any error.Values of the custom request headers you configure on a webhook are masked in the headers shown for each delivery, and wherever your endpoint echoes one back in its response body. A configured value that happens to appear in a response body is masked there too, so a header such as Accept: application/json also masks that text in response bodies. The URL, error message and event data are never altered.

Request Sent

{
  "event": "request.success",
  "timestamp": "2025-01-15T10:30:45.123Z",
  "webhook_id": "wh_abc123",
  "webhook_name": "Slack Notifications",
  "data": {
    "route_id": "route_xyz789",
    "route_name": "payment-api",
    "request": {
      "method": "POST",
      "path": "/v1/charges"
    },
    "response": {
      "status": 200,
      "latency_ms": 342
    }
  }
}

Headers Sent

{
  "Content-Type": "application/json",
  "X-Webhook-Signature": "sha256=abc123...",
  "X-Webhook-ID": "wh_abc123",
  "X-Webhook-Event": "request.success",
  "Authorization": "Bearer ***CONFIGURED***"
}

Response Received

{
  "ok": true
}

Error Message (if failed)

Connection timeout after 30000ms

Filtering Logs

By Success/Failure

Success: ✓ Success Only
         ✗ Failures Only
         All

By Event Type

Event Type: request.success
            request.server_error
            request.completed
            (all)

By Webhook

Webhook: Slack Notifications
         Analytics Logger
         (all)

By Request ID

Correlate with API logs:

Request ID: req_abc123def456

Common Failure Scenarios

Connection Timeout

Log shows:

Error: Request timeout
Response Time: 30000ms
Success: false

Causes:

Your endpoint is too slow
Network connectivity issues
Firewall blocking requests

Solutions:

Increase webhook timeout setting
Optimize your endpoint response time
Check firewall rules

HTTP 4xx Response

Log shows:

Response Status: 401 Unauthorized
Success: false

Causes:

Incorrect authentication configuration
Token expired
Endpoint URL changed

Solutions:

Verify auth credentials
Regenerate tokens if expired
Check endpoint URL

HTTP 5xx Response

Log shows:

Response Status: 500 Internal Server Error
Success: false
Retry Count: 3

Causes:

Your endpoint has a bug
Your endpoint’s dependencies are down
Rate limiting on your endpoint

Solutions:

Check your endpoint logs
Verify endpoint dependencies
Implement proper error handling

Connection Refused

Log shows:

Error: connect ECONNREFUSED 127.0.0.1:3000
Success: false

Causes:

Endpoint server not running
Incorrect port
Firewall blocking

Solutions:

Verify endpoint is running
Check port number
Review firewall rules

Who can see a delivery’s payload

A delivery’s detail is metadata for everyone: its status, timing, response code and any error. Its payload (the event data, the headers and body KnoxCall sent, and your receiver’s response body) is withheld until you click Reveal payload (the API equivalent is GET /admin/webhook-logs/{id}?include=payload). In the dashboard this is a Class B reveal: only an Owner or an Admin can do it (an Editor cannot, even with Reveal secrets turned on; that setting covers secret values, certificates and credentialed workflow tests only), and every use asks for a fresh second factor (an authenticator code, a passkey or a security key; an emailed code does not count). Each use writes a plaintext.reveal entry to the audit log before anything is shown, and counts against the same per-person reveal budget as showing a secret’s value (60 per 5 minutes). If the audit entry cannot be written, or the budget cannot be counted, the request is refused rather than served. The Management API’s delivery logs (/v1/webhooks/{id}/logs) return metadata only. A log policy that withholds a request path’s payload, or the audit-details permission an audit.event delivery also needs, still refuses before your verification is spent. The delivery lists stay metadata-only.

Correlating with API Logs

Each webhook log includes a request_id that links to the original API request:

Find the webhook log entry
Copy the Request ID
Navigate to API Logs
Search by Request ID

This lets you see:

The original request that triggered the webhook
Full request/response details
Client information
Timing breakdown

Webhook Statistics

On the webhook detail page, view aggregate statistics:

Metric	Description
Trigger Count	Total times triggered
Success Count	Successful deliveries
Failure Count	Failed deliveries
Last Triggered	Most recent trigger time
Last Success	Most recent successful delivery
Last Failure	Most recent failed delivery

Log Retention

Webhook logs are retained based on your plan:

Plan	Retention
Starter	7 days
Pro	30 days
Enterprise	90 days

Next Steps

Testing Webhooks

Test your webhook configuration

API Logs

Correlate with API requests

Webhooks Overview

Learn about webhooks

Creating Webhooks

Create your first webhook

Statistics

Level: beginner
Time: 5 minutes

​Webhook Logs

​Viewing Webhook Logs

​All Webhook Logs

​Logs for a Specific Webhook

​Log Entry Details

​Log Entry Detail View

​Request Sent

​Headers Sent

​Response Received

​Error Message (if failed)

​Filtering Logs

​By Success/Failure

​By Event Type

​By Webhook

​By Request ID

​Common Failure Scenarios

​Connection Timeout

​HTTP 4xx Response

​HTTP 5xx Response

​Connection Refused

​Who can see a delivery’s payload

​Correlating with API Logs

​Webhook Statistics

​Log Retention

​Next Steps

Testing Webhooks

API Logs

Webhooks Overview

Creating Webhooks

Statistics

Tags

Webhook Logs

Viewing Webhook Logs

All Webhook Logs

Logs for a Specific Webhook

Log Entry Details

Log Entry Detail View

Request Sent

Headers Sent

Response Received

Error Message (if failed)

Filtering Logs

By Success/Failure

By Event Type

By Webhook

By Request ID

Common Failure Scenarios

Connection Timeout

HTTP 4xx Response

HTTP 5xx Response

Connection Refused

Who can see a delivery’s payload

Correlating with API Logs

Webhook Statistics

Log Retention

Next Steps