KingCaller
Logs

Webhook Logs

Monitor webhook delivery status, payloads, and response codes.

Webhook Logs

Webhook Logs track all HTTP webhook deliveries sent from KC360 to external services.

Accessing Webhook Logs

Navigate to Logs → Webhook Logs

app.kingcaller.ai
Webhook Logs table with columns: Timestamp, URL endpoint, HTTP Method badge (POST, GET), Status Code with color indicators (green 200, red 500, yellow 400), Duration (ms), and an expand arrow for payload details
Webhook delivery log with status codes and response times

Log Entry Details

FieldDescription
TimestampWhen the webhook was sent
URLThe destination URL
MethodHTTP method (POST, GET, etc.)
Status CodeResponse status (200, 400, 500, etc.)
DurationRound-trip time
PayloadRequest body sent
ResponseResponse body received

Status Indicators

StatusMeaning
✅ Success (2xx)Webhook delivered successfully
⚠️ Client Error (4xx)Bad request — check payload format
❌ Server Error (5xx)Destination server error — may retry
⏱️ TimeoutNo response within timeout period

Filtering

FilterOptions
StatusSuccess, Error, Timeout, All
URLSpecific webhook destination
Date rangeTime period

Debugging Failed Webhooks

When a webhook fails:

  1. Click the log entry to see full details
  2. Check the request payload — is it formatted correctly?
  3. Check the response body — the external service may explain the error
app.kingcaller.ai
1
Webhook detail panel showing two code blocks side by side: Request Payload (JSON) on the left and Response Body (error message) on the right, with Status Code 500 badge and a Retry button
Inspect request and response payloads to debug failures
  1. Check the status code — 401 means auth issue, 404 means wrong URL 5. Check the URL — ensure it's correct and the service is running 6. Retry — some webhook types have a manual retry button

Previous

Call Logs

Next

Workflow Logs

On this page