Documentation

Delivery Logs & Testing

The Webhooks settings panel includes a built-in delivery log for each endpoint. Use it to verify that events are reaching your server, diagnose failures, and replay test payloads without triggering real activity.

Viewing Delivery Logs

1

Open Settings → Webhooks

Navigate to Dashboard → Settings → Webhooks.
2

Expand a webhook row

Click the Delivery Logs button on any webhook card. The last 50 delivery attempts are shown, newest first.
3

Inspect each entry

Each row shows the event type, HTTP status code, response time, timestamp, and any error message.

Log Fields

FieldDescription
EventThe event type fired (e.g. post.saved)
StatusHTTP status returned by your endpoint. null if timed out or connection refused.
Response timeRound-trip time in milliseconds from send to final response byte.
SuccessGreen tick = HTTP 2xx. Red cross = any other outcome.
ErrorHuman-readable error for failed deliveries (e.g. Request timed out (10s)).
Delivered atUTC timestamp of the delivery attempt.

Sending a Test Event

1

Expand the webhook card

In Settings → Webhooks, find your webhook and click Send test event.
2

Check the delivery log

The test delivery appears at the top of the Delivery Logs list within a few seconds. Confirm you see a 200 status.

Test events are real HTTP requests

The test event goes through the exact same pipeline as a live event — including HMAC signing. Your signature verification code is fully exercised in the test.

Common Failure Reasons

Error / StatusLikely causeFix
Request timed out (10s)Server took longer than 10 s to respondReturn 200 immediately, then process asynchronously
401Signature verification failedEnsure you read the raw body before JSON parsing
404Endpoint URL path doesn't existDouble-check the URL in Savebase Webhooks settings
500Unhandled error in your receiverCheck your server logs for the exception
Connection refused / null statusServer is down or URL is wrongVerify the server is running and publicly reachable