Skip to Content
SeyloDocs
API referenceNotifications

Update the default alert rules

POST
/api/v1/notifications.updateDefaults

Replaces the panel-wide alert rules. Each event appears at most once; events left out are turned off.

Needs notifications.manage, which owners and admins hold. Available to MCP clients and the assistant.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
rules*array<>
Itemsitems <= 17

Response Body

Success.

application/json
  1. response
rules*array<>
Itemsitems <= 17
Example Request
curl -X POST 'https://example.com/api/v1/notifications.updateDefaults' \  -H 'Content-Type: application/json' \  -d '{  "rules": [    {      "event": "crash",      "enabled": true,      "channelIds": [        "string"      ]    }  ]}'
Example Response
{  "rules": [    {      "event": "crash",      "enabled": true,      "channelIds": [        "string"      ]    }  ]}

Update a notification channel POST

Changes a channel's name, settings, enabled flag or default flag. The kind cannot change. Secret fields left out of config keep their stored value. Needs `notifications.manage`, which owners and admins hold. Available to MCP clients and the assistant.

Set a service's alert rules POST

Makes a service follow the default alert rules (useDefaults true) or use its own (useDefaults false with rules). Rules for non-service events are refused. Needs `services.alerts` on the service (a grant on its project covers it). Available to MCP clients and the assistant.