Deliveries and retries

Plan availability

Webhooks is available on Pro and Business. See the plan comparison.

DomainDash records every webhook it tries to send. You can see what was delivered and what your endpoint returned, and replay anything that didn't get through. To set up an endpoint, see outbound webhooks.

How a delivery works

When an event fires for a site in your team, DomainDash creates a delivery for each endpoint subscribed to that event and sends it as a signed POST request to your endpoint's URL.

Your endpoint has 10 seconds to respond. DomainDash treats any 2xx response as success. Anything else (a 4xx, a 5xx, a timeout, or no response at all) counts as a failure and is retried. DomainDash doesn't follow redirects, so a 3xx response counts as a failure too.

Recent deliveries

The Recent deliveries table on Settings → Developers shows your most recent deliveries, newest first. Each row shows:

• Event — the event type, such as site.went_down.
• Status — pending, success, or failed.
• Response — the HTTP status code your endpoint returned (or a dash if there wasn't one).
• Attempts — how many times DomainDash has tried to deliver it.
• Time — when it was delivered, or when it was created if it hasn't been delivered yet.

Use the table to confirm an event was sent, see what your endpoint returned, and spot anything that failed.

Retries with backoff

DomainDash makes up to 5 attempts per delivery. After a failed attempt, retries follow at 10 seconds, 1 minute, 5 minutes and 30 minutes, so a briefly unavailable endpoint has time to recover.

If the fifth attempt fails, DomainDash stops retrying that delivery. You can replay it once your endpoint is working.

Because deliveries can be retried, your endpoint should be idempotent: use the webhook-id header to recognise an event you've already processed, so a retry doesn't process it twice.

When an endpoint is disabled

DomainDash disables an endpoint after 20 failed deliveries in a row. Any successful delivery resets the count. A disabled endpoint shows a status of "Too many failed deliveries" and stops receiving new events.

To bring it back, fix whatever was wrong on your side, then edit the endpoint and re-enable it. Re-enabling resets the failure count.

Replaying a delivery

To re-send a delivery, whether or not it failed, use Replay on its row. DomainDash re-queues that exact delivery and sends it again, with a fresh attempt count and the same signed payload.

Replay is useful when your endpoint was briefly down and missed events, or when you've fixed a bug in how your endpoint handles a particular event type.

Only the team owner and admins can replay deliveries.

Frequently asked questions

What counts as a successful webhook delivery?

Any 2xx response from your endpoint within 10 seconds. Anything else (a 3xx redirect, a 4xx, a 5xx, a timeout, or no response at all) counts as a failure and is retried.

What happens when a delivery fails?

DomainDash retries it, up to 5 attempts in total. The retries follow at 10 seconds, 1 minute, 5 minutes and 30 minutes, which gives a briefly unavailable endpoint time to recover.

Why was my endpoint disabled?

DomainDash disables an endpoint after 20 failed deliveries in a row, and it shows a status of "Too many failed deliveries". To bring it back, fix whatever was wrong on your side, then edit the endpoint and re-enable it.

Can I re-send a webhook that failed?

Yes. Use Replay on the delivery's row. DomainDash sends the same signed payload again with a fresh attempt count. Only the team owner and admins can replay deliveries.

Related

• Outbound webhooks for setting up endpoints, events, and the signing secret
• How incidents work for the events that trigger deliveries
• Plans and pricing for which plans include webhooks