List notification subscription executions

GET

Returns stored execution records for a notification subscription.

Each record shows how the subscription filter evaluated for a processed alert event, including whether the filter matched.

Path parameters

• subscriptionId: required string; notification subscription identifier

Query parameters

• alertId: optional string; filter records to one alert identifier
• matched: optional; all, true, or false; defaults to all
• from: optional date-time; lower bound for processedAt
• to: optional date-time; upper bound for processedAt
• limit: optional integer; defaults to 50; maximum 200
• cursor: optional string; opaque cursor for pagination

Request behavior

• Results are limited to the caller's environment
• Records are sorted by processedAt descending, then by record id descending
• alertId uses the alert id without the environment prefix
• include is not supported on this endpoint
• If the subscription does not exist in the caller's environment, the endpoint returns 404

Response

• 200 OK

Field	Type	Description
items	array	Execution records for the subscription
items[].id	string	Execution record identifier
items[].alertEventId	string	Alert event identifier without environment prefix
items[].filterMatched	boolean	Whether the subscription filter matched that event
items[].processedAt	datetime	When the execution record was stored
nextCursor	string or null	Cursor for the next page

Errors

• 400: invalid subscriptionId or invalid query parameter value
• 404: subscription not found

Example

{
  "items": [
    {
      "id": "67f15cf4442fa9128442be12",
      "alertEventId": "alert-123|7",
      "filterMatched": true,
      "processedAt": "2026-03-26T09:12:44.218Z"
    },
    {
      "id": "67f15c80442fa9128442bdff",
      "alertEventId": "alert-123|6",
      "filterMatched": false,
      "processedAt": "2026-03-26T09:11:12.004Z"
    }
  ],
  "nextCursor": "eyJwcm9jZXNzZWRBdCI6IjIwMjYtMDMtMjZUMDk6MTE6MTIuMDA0WiIsImlkIjoiNjdmMTVjODA0NDJmYTkxMjg0NDJiZGZmIn0"
}

Notes

• Execution records are stored when the notification processor evaluates a subscription against an alert event, even when the filter does not match
• Use Get notification subscription execution to inspect the saved filter and evaluation context for a single record