Once your endpoint is working again, you can turn the webhook back on yourself in a few clicks.
Why SendPost disables webhooks
Every time SendPost sends an event to your webhook, your endpoint needs to respond with HTTP 200 OK. A delivery counts as failed when your endpoint returns an error, refuses the connection, or doesn't respond successfully in time.
A single failure won't disable your webhook. SendPost retries each failed event and only disables the webhook after a long run of sustained failures:
What happens | Details |
Retries per event | 4 attempts, spaced 30 seconds, 60 seconds, 120 seconds and 240 seconds apart |
When an event is marked as failed | If it still hasn't been delivered after 7.5 minutes of retries |
When the webhook is disabled | After 500 consecutive failed events |
Why we disable instead of retrying forever
An endpoint that fails hundreds of events in a row holds connections open and backs up the delivery queue. Disabling the webhook keeps event delivery fast and reliable for your account and for everyone else on the platform.
How you'll know it happened
Email: We send an email to your account's notification address when a webhook is disabled.
Dashboard: The webhook's status changes to Disabled in Settings → Webhooks.
Your tools: Data that depends on the webhook, such as reporting in your CRM or analytics tool, stops updating.
What to check before you re-enable
Important: If you turn the webhook back on while your endpoint is still failing, it will hit the failure limit again and disable itself a second time. Fix the endpoint first.
Confirm each of these before you re-enable:
It returns 200 OK. Your endpoint acknowledges each event with a 2xx response, not a 4xx or 5xx error.
It's reachable. The domain resolves, the TLS (SSL) certificate is valid, and the correct port is open and listening.
It accepts the payload. Your receiver can read the event body instead of rejecting it.
It keeps up with volume. Your endpoint responds in time, even when you're sending large campaigns and events arrive quickly.
Downstream services are live. If your endpoint forwards events to another tool, such as a CRM or marketing platform, confirm that tool is accepting requests too.
How to re-enable your webhook
In your SendPost dashboard, go to Settings → Webhooks.
Find the webhook marked Disabled.
Make sure you've worked through the checklist above, then enable the webhook.
Send a test event and confirm your endpoint returns 200 OK.
Keep an eye on the webhook for a while to confirm events are flowing normally.
Managing more than one account? Webhooks are set up inside each individual account. Open the specific account the webhook belongs to, rather than a team-wide or combined view, to see and re-enable it.
Frequently asked questions
Will I get the events that failed while the webhook was disabled?
Missed events can be replayed after re-enabling the webhook.
My endpoint is working but the webhook keeps getting disabled. What now?
Check your API endpoint status and ensure it's not experiencing frequent downtime. Then contact SendPost support and include:
The webhook's name or ID
The approximate date and time it was disabled
Our team will check the delivery logs and tell you exactly why events were failing.