Webhook Delivery Logs — How to Monitor and Debug Your Webhook Events

Learn how to access webhook delivery logs, understand delivery statuses, filter logs, and troubleshoot failed deliveries

What are Webhook Delivery Logs?

DoubleTick sends real-time events to your system via webhooks — things like message status updates, chat assignments, incoming messages, and more. Every time an event is sent to your webhook URL, it counts as a delivery attempt.

The Logs tab in Webhook settings gives you full visibility into every delivery attempt — whether it succeeded, failed, or was retried. This is useful when you want to verify your integration is working correctly or figure out why a specific event did not reach your system.

---

How to Access Webhook Delivery Logs

1. From the left navigation panel, click Settings.

2. Scroll down and click Webhooks.

3. On the Webhooks page, click the Logs tab at the top.

---

What You See on the Logs Page

The page is split into two panels — a list on the left and a detail view on the right.

Left Panel — Delivery Attempt List

Each row represents one delivery attempt. It shows:

Element	What It Shows
Webhook Name	The name of the webhook that was triggered
Webhook URL	The destination URL the event was sent to
Timestamp	Date and time of the delivery attempt
Status Badge	A colour-coded label showing the outcome — Success, Failed, Retried, or Exhausted

Click any row to see its full details in the right panel.

Right Panel — Delivery Attempt Details

When you click a delivery attempt, the right panel shows a complete breakdown:

Field	What It Shows
Webhook Name	Which webhook configuration triggered this delivery
Status	The outcome of this attempt
Webhook URL	The full destination URL
HTTP Status	The response code from your server — 200 means success
Latency	How long your server took to respond (e.g., 73 ms)
Timestamp	Exact date and time
Attempt	Which retry attempt this was (e.g., Attempt 1, Attempt 2)
Event Type	The type of event that triggered the webhook (e.g., Message Status Update)
Request Headers	Headers sent with the webhook request (shown as JSON)
Request Body	The full payload sent to your endpoint (shown as JSON)
Response Headers	Headers returned by your server
Response Body	The response your server sent back

---

Understanding Delivery Statuses

Every delivery attempt is tagged with one of four statuses:

Status	What It Means
Success	Your server received the event and returned a successful response
Failed	The delivery failed — your server returned an error or was unreachable
Retried	The first attempt failed and DoubleTick automatically retried
Exhausted	All retry attempts have been made and the delivery still failed

---

How to Filter and Search Logs

Use the filters at the top of the Logs page to quickly find specific webhook logs.

• Search by name or URL: Enter the webhook name or destination URL in the Search bar.

• Filter by status: Select Success, Failed, Retried, or Exhausted from the All Statuses dropdown.

• Filter by event type: Choose an event from the All Event Types dropdown. You can also search within the dropdown.

• Filter by date: Use the All Time dropdown to view logs from Today or select a custom date range.

---

How to Debug a Failed Webhook

1. Go to the Logs tab.

2. Click the All Statuses dropdown and select Failed or Exhausted.

3. Click on a failed delivery attempt from the list.

4. In the right panel, check the HTTP Status — this tells you what error your server returned.

5. Review the Request Body to confirm the correct data was sent.

6. Review the Response Body to see what your server responded with.

7. Share these details with your developer to fix the issue on the server side.

How to Verify a Specific Event Was Delivered

1. Use the Search bar to find the webhook by name.

2. Click the All Event Types dropdown and select the event you are looking for (e.g., Message Status Update).

3. Check if a Success entry exists for that event.

4. Click on it to view the full request and response details.

How to Check Response Times

1. Click on any delivery attempt in the list.

2. In the right panel, look at the Latency field.

3. This shows how long your server took to respond to DoubleTick's webhook call.

If latency is consistently high, it may indicate a performance issue on your server side.

---

Summary

In this article, you learned how to access webhook delivery logs, what the four delivery statuses mean, how to filter logs by status, event type, and date, and how to debug failed deliveries and verify successful ones.