Webhook auto-disable: better delivery to URLs that work

1MSG now limits delivery to URLs that do not respond. This helps events reach URLs that work. URLs that work, and the rest of the product, do not change: events still arrive as they did.

Faster delivery to URLs that work

Before, 1MSG tried to send every event to every webhook URL you set — even if that URL had been dead for a long time. For example, you forgot to remove a test URL, you did not renew hosting, you changed a domain, or you changed an integration URL and did not update it with us. Each try uses the queue and slows down URLs that still work.

Now we stop sending to URLs that do not respond, so events reach URLs that do.

How it works

This does not apply to URLs that work. If the URL works, events arrive as they did. A failure is a timeout, a network error, or HTTP 5xx, 401, 403, 404, 410, or 429 — not every status code.

If a URL stops responding, we do not stop it at once. Delivery continues. After a second failure we send a warning by email, and events still go out. If the URL still does not respond after 10 minutes, we pause sending to it.

Then 1MSG checks if the URL is back: after 15 minutes, then after one hour, then after six hours. A 2xx response starts delivery again by itself. If all three checks fail, delivery to that URL stays paused, and we email you that it has stopped.

Six hours is the last check. The URL stays off. If there is no 2xx, the only way to start delivery again is to set the webhook URL again.

How to restore delivery

If you got an email, or events stopped arriving at one of your URLs, use GET /webhook or GET /settings. The status for each URL shows which one is paused, so you know which URL to turn on again.

Delivery starts again by itself if a check gets a 200 in the first six hours. If the URL never responded, you can turn it on yourself: POST /webhook again and send the full list of URLs you want to keep. This request replaces the whole list. If you send one URL and you had three, the other two are removed.

Warning and disabled emails go to the channel owner. If you do not want them, you can unsubscribe.

Method reference, if you need it later: GET /webhook