LEleakradar
Notifications

Pause or resume a notification method

Changed on

Resume a notification method that was suspended after repeated delivery failures, or pause / resume it yourself.

LeakRadar suspends a method when its deliveries keep failing in a way that shows the destination is broken (deleted webhook, revoked bot token, endpoint down for a day). A suspended method is retried every few hours and resumes on its own as soon as one delivery goes through; editing its destination or a successful test also resumes it. Notifications using a suspended or paused method keep running: their results stay in the monitoring history, they are just not sent.

Errors

  • 401 Authentication required.
  • 404 Notification method not found.
patch/notification_methods/{method_id}/active

Request

Path parameters

method_idinteger required

ID of the notification method.

Request body

is_activeboolean required

true resumes a suspended or paused method (its failure count starts over), false pauses it: nothing is sent to it, the notifications using it keep running.

Example request

{
  "is_active": true
}

Response

Method updated; the body is the method with its new status.

idinteger required

Notification method ID.

type'email' | 'slack' | 'telegram' | 'webhook' | 'discord' required
namestring nullable

User-given label of this channel, null when unnamed.

valuestring required

Primary destination (email address, webhook URL, channel ID, etc.).

second_valuestring nullable

Secondary value (e.g. Telegram chat ID).

extra_emailsstring[] nullable

Additional email recipients delivered as BCC (email methods only, max 4).

timestampstring date-time required

Creation date of this notification method.

status'active' | 'suspended' | 'paused'

Delivery state. active: alerts are delivered. suspended: deliveries kept failing, so LeakRadar stopped sending; it retries every few hours and resumes on the first delivery that goes through. paused: paused by you. Alerts using a suspended or paused method keep running; their results stay in the monitoring history.

suspended_atstring date-time nullable

When the method was suspended or paused.

consecutive_failuresinteger

Failed deliveries in a row that prove the destination is broken (gone, refused or down), since the last successful one.

failing_sincestring date-time nullable

First failure of the current streak.

last_failure_atstring date-time nullable

Last failed delivery.

last_success_atstring date-time nullable

Last successful delivery, test sends included.

last_errorstring nullable

Why the last delivery failed.

Changes