> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/webhooks/webhook-delivery-logs-how-to-monitor-and-debug-your-webhook-events.md).

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

#### <mark style="color:$primary;">**What are Webhook Delivery Logs?**</mark>

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.

***

<figure><img src="/files/YtWCBi50eIPAGH1KRH9A" alt=""><figcaption></figcaption></figure>

#### <mark style="color:$primary;">**How to Access Webhook Delivery Logs**</mark>

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.

***

#### <mark style="color:$primary;">**What You See on the Logs Page**</mark>

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

<figure><img src="/files/97exdSqrEVBB9e9gWNsg" alt=""><figcaption></figcaption></figure>

**Left Panel — Delivery Attempt List**

Each row represents one delivery attempt. It shows:

<table><thead><tr><th width="176">Element</th><th>What It Shows</th></tr></thead><tbody><tr><td>Webhook Name</td><td>The name of the webhook that was triggered</td></tr><tr><td>Webhook URL</td><td>The destination URL the event was sent to</td></tr><tr><td>Timestamp</td><td>Date and time of the delivery attempt</td></tr><tr><td>Status Badge</td><td>A colour-coded label showing the outcome — Success, Failed, Retried, or Exhausted</td></tr></tbody></table>

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

<figure><img src="/files/adt2pSGLzjAdJQtEQQZq" alt=""><figcaption></figcaption></figure>

**Right Panel — Delivery Attempt Details**

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

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

***

<figure><img src="/files/7g9IGqJLa0p2OX7tA8Ix" alt=""><figcaption></figcaption></figure>

#### <mark style="color:$primary;">**Understanding Delivery Statuses**</mark>

Every delivery attempt is tagged with one of four statuses:

<table><thead><tr><th width="171">Status</th><th>What It Means</th></tr></thead><tbody><tr><td><strong>Success</strong></td><td>Your server received the event and returned a successful response</td></tr><tr><td><strong>Failed</strong></td><td>The delivery failed — your server returned an error or was unreachable</td></tr><tr><td><strong>Retried</strong></td><td>The first attempt failed and DoubleTick automatically retried</td></tr><tr><td><strong>Exhausted</strong></td><td>All retry attempts have been made and the delivery still failed</td></tr></tbody></table>

***

#### <mark style="color:$primary;">How to Filter and Search Logs</mark>

<figure><img src="/files/4HCPjk3Q3y226T8qIpll" alt=""><figcaption></figcaption></figure>

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.

***

#### <mark style="color:$primary;">**How to Debug a Failed Webhook**</mark>

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.

#### <mark style="color:$primary;">**How to Verify a Specific Event Was Delivered**</mark>

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.

#### <mark style="color:$primary;">**How to Check Response Times**</mark>

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.

***

#### <mark style="color:$primary;">**Summary**</mark>

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.doubletick.io/webhooks/webhook-delivery-logs-how-to-monitor-and-debug-your-webhook-events.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.