Get notification subscription execution

GET

Returns one stored execution record for a notification subscription.

Use this endpoint when you need to inspect the saved filter and the evaluation context for a specific execution.

Path parameters

• subscriptionId: required string; notification subscription identifier
• executionId: required string; execution record identifier

Response

• 200 OK

Field	Type	Description
id	string	Execution record identifier
subscriptionId	string	Notification subscription identifier
alertEventId	string	Alert event identifier without environment prefix
filterMatched	boolean	Whether the subscription filter matched that event
processedAt	datetime	When the execution record was stored
filter	object or null	Filter saved on the subscription at evaluation time
filterEvaluationContext	object or null	Evaluation context used when the filter was executed

Errors

• 400: invalid subscriptionId or executionId
• 404: subscription not found or execution not found for that subscription in the caller's environment

Example

{
  "id": "67f15cf4442fa9128442be12",
  "subscriptionId": "65f3b1d8e83b5d0a4af00c91",
  "alertEventId": "alert-123|7",
  "filterMatched": true,
  "processedAt": "2026-03-26T09:12:44.218Z",
  "filter": {
    ">=": [
      {
        "var": "computed.impact.max_24h"
      },
      3
    ]
  },
  "filterEvaluationContext": {
    "event": {},
    "computed": {
      "impact": {
        "current": 3,
        "max_24h": 4
      }
    }
  }
}

Notes

• This endpoint is useful when reviewing why a subscription matched or did not match a specific event
• filterEvaluationContext reflects the runtime evaluation context saved by the notification processor
• To build new filter test cases, you can use the related alert event from the Alerts API as a starting point and then submit a modified event body to Test notification filter