# Webhook Delivery Logs

Debug webhook deliveries and view retry status

Every webhook delivery — successful or failed — is logged in Mailnaptic. The delivery logs are your primary tool for debugging integration issues, verifying that events are being sent, and understanding retry behavior.

## Accessing delivery logs

1. Navigate to **Organization → Webhooks**.
2. Click on the webhook endpoint you want to inspect.
3. Select the **Deliveries** tab.

The log shows a chronological list of all delivery attempts, with the most recent at the top.

## Log entry details

Each delivery log entry contains:

| Field | Description |
| --- | --- |
| **Event type** | The event that triggered the delivery (e.g., `email.bounced`) |
| **Timestamp** | When the delivery attempt was made |
| **Status code** | The HTTP status returned by your endpoint |
| **Response time** | How long your endpoint took to respond (in milliseconds) |
| **Attempt number** | Which attempt this is (1 = first try, up to 6 total) |
| **Status** | *Delivered*, *Retrying*, or *Failed* |

Click on any entry to expand it and see the full **request body** (the JSON payload sent) and the **response body** returned by your server (first 1 KB).

## Understanding delivery statuses

- **Delivered:** Your endpoint returned a `2xx` status code. The delivery is complete.
- **Retrying:** The delivery failed and is scheduled for a retry. The next attempt time is shown.
- **Failed:** All retry attempts have been exhausted (5 retries after the initial attempt). The event was not successfully delivered.

## Filtering the log

Use the filters above the log table to narrow down entries:

- **By status:** Show only delivered, retrying, or failed entries.
- **By event type:** Filter to a specific event like `contact.created`.
- **By date range:** Limit results to a specific time period.

## Troubleshooting with logs

### Consistent 4xx errors

If every delivery returns a `4xx` status, the issue is usually with your endpoint's URL or authentication. Double-check that the URL is correct and that your endpoint does not require API keys or tokens that Mailnaptic is not sending.

### Intermittent 5xx errors

Occasional `5xx` errors often indicate your server is under load or experiencing transient issues. Mailnaptic's retry mechanism will handle these automatically. If `5xx` errors are persistent, investigate your server's health and error logs.

### Timeouts

Mailnaptic waits **10 seconds** for a response. If your endpoint performs heavy processing, consider accepting the webhook immediately (return `200`) and processing the data asynchronously in a background job.

## Log retention

Delivery logs are retained for **30 days**. After that period, entries are automatically purged. If you need longer retention for compliance or auditing, forward webhook payloads to your own logging infrastructure.

> **Tip:** If you see a failed delivery for an important event, you can re-send it by clicking the **Retry** button on the expanded log entry.
