---
title: "How to retry or resend failed Smartlead webhooks"
description: "Smartlead retries failed webhooks automatically for about 28 hours. After that, fix your endpoint and resend failed events with the retrigger API."
url: https://helpcenter.smartlead.ai/en/articles/402-how-to-retry-or-resend-failed-smartlead-webhooks
collection: "API, Integrations, and Webhooks"
updated: 2026-11-17
language: en
---

# How to retry or resend failed Smartlead webhooks

Smartlead retries failed webhooks automatically for about 28 hours. After that, fix your endpoint and resend failed events with the retrigger API.

When your server doesn't accept a webhook, Smartlead tries again on its own. If the retries run out, you can resend failed events for a campaign with the API.

**Most failures fix themselves once your endpoint is back.** Smartlead retries each failed event up to 8 times over about 28 hours.

## Before you start

-   Your endpoint must accept a `POST` request with a JSON body and reply with a 2xx within 60 seconds.
    
-   To resend events with the API, you need your Smartlead API key.
    

## Step 1: Fix your endpoint

1.  Find out why the event failed. Check your server logs, or call `GET /api/v1/webhook-event-logs` with your API key to see deliveries from the last 3 days.
    
2.  Fix the cause. For example, correct the URL, make the endpoint reply faster, or fix your signature check.
    
3.  Make sure your endpoint replies with a 2xx before doing heavy processing.
    

## Step 2: Let automatic retries run

Smartlead retries every failed event about 1 minute, 5 minutes, 30 minutes, 2 hours, 5 hours, 10 hours and 10 hours after the last try.

It does not retry when your server replies `400`, `413` or `422`. Those replies mean the request will never be accepted, so fix the cause and use Step 3.

## Step 3: Resend failed events with the API

Use this when the automatic retries have run out, or your server rejected the events with a `400`, `413` or `422`.

1.  Note the campaign ID and the time window when the events failed.
    
2.  Send this request, with `fromTime` and `toTime` in ISO format covering the failures:
    

```javascript
POST https://server.smartlead.ai/api/v1/campaigns/{campaign_id}/webhooks/retrigger-failed-events?api_key=<your-api-key>

{ "fromTime": "2026-11-01T00:00:00Z", "toTime": "2026-11-02T00:00:00Z" }
```

3.  Smartlead resends the failed events in that window in small batches.
    
4.  Check progress with `GET /api/v1/campaigns/{campaign_id}/webhooks/summary`.
    

## Good to know

-   **Use the event ID to avoid duplicates.** Each event keeps the same ID in the `event_id` field and the `webhook-id` header on every retry. Skip IDs you've already processed.
    
-   Only events that failed in the last 2 weeks can be resent.
    
-   Events that happened before you created the webhook were never sent, so they can't be resent.
    
-   If every delivery in the window succeeded, the retrigger finds nothing to resend. Check your own server's logs for those requests.
    
-   Slack webhooks have no **Send Test** button. Trigger a real event to check them.
    

Still stuck? Contact support from the chat in your Smartlead dashboard. Include the campaign ID, the time window and the response from the retrigger request.

## Related articles

-   [How To Resolve Webhook Failures](https://helpcenter.smartlead.ai/en/articles/417.md)
    
-   [Secure Your Smartlead Webhooks with Signing (HMAC)](https://helpcenter.smartlead.ai/en/articles/470.md)
    
-   [Set Up Smartlead Webhooks for Campaign Automation](https://helpcenter.smartlead.ai/en/articles/35.md)
