Dry-run: evaluate a policy's match rules against a supplied incident context
Documentation Index
Fetch the complete documentation index at: https://docs.devhelm.io/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
API key (dh_live_...) or Auth0 JWT token
Path Parameters
Body
Event context for a dry-run match evaluation against a notification policy
Incident severity to test against (e.g. DOWN, DEGRADED, MAINTENANCE)
Monitor UUID to test against (monitoring events)
Affected region identifiers to test against (monitoring events)
Affected region identifiers to test against (monitoring events)
Incident event type to test against — short form (e.g. created, resolved, reopened) or full form (e.g. incident.created)
Monitor check type to test against (e.g. HTTP, DNS, MCP_SERVER)
Service catalog UUID to test against (status data events)
Component name to test against (status data events, e.g. "Actions")
Resource group UUIDs the entity belongs to, for resource_group_id_in rules
Resource group UUIDs the entity belongs to, for resource_group_id_in rules
Response
OK
Result of a dry-run match evaluation against a notification policy