Webhook delivery failures

A webhook subscription isn’t delivering events to your endpoint, or deliveries are failing.

​

Quick checks

• Open Settings > Integrations > Webhooks, expand the subscription, and read its delivery log first — the status, response code, and error on each attempt point straight at the cause.

​

Cause: the subscription is disabled

How to check: Confirm Enabled is on for the subscription. How to fix: Turn it on, then replay any deliveries you missed from the delivery log.

​

Cause: the event type isn’t subscribed

How to check: If you never see a delivery row at all for an event you expect, the subscription’s event types don’t include it — see the event catalog. How to fix: Add the event type to the subscription.

​

Cause: your endpoint is unreachable

How to check: The delivery log’s error mentions a connection failure, timeout, or DNS error rather than a response code. How to fix: Confirm the URL is correct and reachable from the public internet — not an internal-only address.

​

Cause: your endpoint returned a non-2xx response

How to check: The delivery log shows the response code your endpoint sent. How to fix: A 401 usually means signature verification is failing on your end — see Verify signatures. A 4xx or 5xx means your endpoint rejected or errored on the payload; check your endpoint’s own logs.

​

Cause: your endpoint was too slow

How to check: The delivery log shows a timeout with no response code. How to fix: Respond within a few seconds. If your processing takes longer, acknowledge immediately and do the work asynchronously.

​

Cause: delivery was exhausted after repeated failures

How to check: The delivery log shows status Exhausted — Get2Dial stops retrying after 6 attempts over about 24 hours. How to fix: Fix your endpoint, then select Replay on the exhausted delivery.

​

If none of this worked