Skip to main content
Alerting & Response/Alert Channels & Integrations
GETAlertingSince 1.0SynchronousAuth Required

GetAlertNotificationRetryQueueStats

Retrieve retry queue statistics and list of pending/dead notifications

Execution Availability

Try It Out

Submit a mock request using the current auth context and example-driven inputs.

Request Inputs

This API requires no request parameters.

Responses

200 OK

On success, this API returns the following response structure.

  • pendingCountInteger

    Number of notifications pending retry

    Example: 5

  • deadCountInteger

    Number of dead-lettered notifications

    Example: 2

  • itemsList

    List of retry queue entries

    Example: (nested array)

    • notificationIdString

      Unique identifier of the notification

      Example: notif-001

    • alertIdString

      Alert identifier this notification belongs to

      Example: alert-789xyz

    • channelTypeString

      Channel type used for delivery (email, webhook, etc.)

      Example: email

    • payloadString

      Serialized notification payload

      Example: {...}

    • attemptCountInteger

      Number of delivery attempts made so far

      Example: 3

    • maxAttemptsInteger

      Maximum number of retry attempts allowed

      Example: 5

    • nextRetryAtString

      Scheduled time for the next retry attempt

      Example: 2026-01-15T08:00:00Z

    • lastErrorString

      Error message from the last failed attempt

      Example: connection timeout

    • statusString

      Current status: pending, dead, or retrying

      Example: dead

    • createdAtString

      Timestamp when this retry entry was created

      Example: 2026-01-15T08:00:00Z

Endpoint

GET/api/v1/alerting/notification-retry

/api/v1/alerting/notification-retry

Operation ID

GetAlertNotificationRetryQueueStats

Permalink

Request Example

curl -X GET '{host}/api/v1/alerting/notification-retry' -H 'Authorization: Bearer {token}'

Response Example

200
{
  "pendingCount": 5,
  "deadCount": 2,
  "items": [
    {}
  ]
}

Change History

This API has no change history records yet.

View all change history