Troubleshoot outbound webhooks

Most webhook problems come from endpoints that don't meet the delivery requirements or that have been automatically disabled after repeated failures. Match your symptom below for the cause and fix.

My endpoint was automatically disabled

An endpoint is automatically disabled after 10 consecutive exhausted deliveries — deliveries that failed and weren't successfully delivered after retries. When this happens, the team owner receives an email linking to Settings → Integrations. Fix your server, then re-enable the endpoint from Settings → Integrations → Webhooks. Re-enabling resets the failure counter.

Common causes of exhausted deliveries are an endpoint that doesn't respond within 10 seconds, returns a non-2xx status, or can't be reached.

My endpoint URL was rejected when I saved it

Eventually only accepts public HTTPS URLs. Plain HTTP URLs and private, loopback, or link-local hosts are rejected at save time. Use a public HTTPS URL for your endpoint.

My deliveries aren't arriving

Check that the endpoint is enabled and that you've selected at least one event type on the endpoint. Use Send test event to see the exact reason a delivery fails — it shows the receiver's HTTP response. Test events are limited to 5 per minute per client IP.

If you downgraded to a plan with a lower endpoint cap, deliveries to endpoints over the new cap are paused until you remove endpoints or upgrade. See Set up outbound webhooks for how endpoint caps work.

My receiver got a delivery it couldn't verify

Verify the signature against the raw request body, before any JSON parsing or re-serialization. If you lost the signing secret, rotate it from the endpoint to generate a new one, then update your receiver. See Verify Eventually webhook signatures for the verification steps.