Enable / Disable Alert Rule
Flips the enabled flag on a rule without touching the rest of its configuration. Disabled rules are persisted but skipped by the evaluator — useful for muting an alert during a planned change without losing the threshold, channels, or history.
Path parameters
uuid string (uuid) Req
Alert rule UUID.
Request body
enabled boolean Req
Target state. The endpoint sets the flag exactly to this value — it is idempotent, not a flip.
Response (204 No Content)
Empty body. Read the rule back to confirm the new enabled value.
Errors
400 Bad Request
Invalid JSON body.
401 Unauthorized
Missing auth.
403 Forbidden
Plan doesn't include
metric_alerts.404 Not Found
No rule with that UUID owned by the caller.
Request — mute the rule
curl -X POST "https://api.ngris.com/v1/traffic/alerts/<uuid>/toggle" \
-H "X-API-KEY: <your_api_key>" \
-H "Content-Type: application/json" \
-d '{"enabled": false}'
Response
HTTP/1.1 204 No Content