webhook.disabled
When Signals sends webhook.disabled, its payload and how to handle it in Node.js, Python and Java.
Signals turned another subscriber's endpoint off because it answered 410 or kept failing. You are never told about your own.
Payload
Every delivery is the envelope type, timestamp, sequence and data; the delivery's id is the webhook-id header. See Verify webhooks.
{
"type": "webhook.disabled",
"timestamp": "2026-10-25T08:00:02.000Z",
"sequence": 1059,
"data": {
"subscriber": "ovok-sub-4f2a9c",
"reason": "failing",
"disabledAt": "2026-10-30T08:00:00.000Z",
"failingSince": "2026-10-25T08:00:00.000Z",
"lastFailureAt": "2026-10-30T07:58:00.000Z"
}
}| Field | Meaning |
|---|---|
subscriber | The subscriber whose endpoint was turned off. |
reason | gone (it answered 410) or failing. See When deliveries fail. |
disabledAt, failingSince, lastFailureAt | When it was turned off, when the failures began, and the latest one. failingSince and lastFailureAt can be null. |
Handle the event
Verify the delivery first (Verify webhooks), then act on the verified event as in Handle an event.
export async function handle(webhookId, event) {
if (!(await firstTime(webhookId))) return;
const { data } = event;
switch (event.type) {
case 'webhook.disabled':
await alertEndpointOwner(data.subscriber, data.reason);
break;
default:
break;
}
}Related
Last updated on