company logo

Help center

Go to Smartlead.ai
API Documentation
All collectionsAPI, Integrations, and Webhooks Webhook not delivering? How to fix webhook failures

Webhook not delivering? How to fix webhook failures

Find out why a Smartlead webhook failed, fix your endpoint or webhook setup, and get missed events delivered again with retries or the retrigger API.

A webhook delivery fails when your server doesn't reply with a 2xx status, or doesn't reply within 60 seconds. This article covers the common causes and how to fix each one.

Failed deliveries are retried automatically. Smartlead tries up to 8 times over about 28 hours, unless your server replies 400, 413 or 422.

Common causes and fixes

No events arrive at all

  1. Check that the webhook has the right events selected under Event Type.

  2. Check that an event of that type has actually happened since you created the webhook. Events from before the webhook existed are not sent.

  3. Check for a higher-level webhook. Each event goes to only one webhook (plus one Slack webhook). An account-level webhook beats a client-level one, which beats a campaign-level one. At the same level, the most recently updated webhook wins.

  4. To send an event to a campaign webhook instead, remove that event from the account-level webhook in Settings → Webhook.

Untracked Replies can only be added to an account-level or client-level webhook, because untracked replies aren't tied to a campaign.

Your server replies with a 4xx

  1. Check the webhook URL for typos, and that it accepts a POST request with a JSON body.

  2. Check that the URL doesn't need a login or extra headers that Smartlead doesn't send.

  3. If you check webhook signatures, reply 401 when a signature doesn't match. Smartlead retries a 401 but never retries 400, 413 or 422.

Your server replies with a 5xx or times out

  1. Reply with a 2xx straight away, then do the heavy processing in the background.

  2. Check your server logs for slow database calls or app errors.

Smartlead waits up to 60 seconds for each reply, then counts it as failed and retries later.

Your server replies 429 Too Many Requests

  1. Use a production receiver rather than a free test tool with low limits.

  2. Add a queue so bursts of events don't hit your limit.

If your 429 reply includes a Retry-After header, Smartlead waits that long before retrying, up to 1 hour.

Test your webhook

  1. Go to Settings → Webhook and click the pencil icon on your webhook.

  2. Select exactly one event under Event Type.

  3. Click Send Test.

A test sends fixed sample data once and is never retried. Slack webhooks have no Send Test button, so trigger a real event to check them.

Good to know

  • Each event has an ID that stays the same on every retry. Store it and skip events you've already processed.

  • Retries are spaced out: about 1 minute, 5 minutes, 30 minutes, 2 hours, 5 hours, 10 hours and 10 hours apart.

  • To see recent deliveries, call GET /api/v1/webhook-event-logs with your API key. It returns the last 3 days.

  • To send failed events again after you fix your endpoint, call the retrigger API below. It covers the last 2 weeks.

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" }

Still stuck? Contact support from the chat in your Smartlead dashboard. Include the webhook URL's domain, the campaign ID, the event type and the time of a failed event.

Related articles

  • How to Retry or Resend Webhooks

  • Secure Your Smartlead Webhooks with Signing (HMAC)

  • Webhook not sending triggers

  • Set Up Smartlead Webhooks for Campaign Automation

Did this answer your question?
😞
😐
😁