Skip to Content
SeyloDocs
API referenceNotifications

Set a service's alert rules

POST
/api/v1/notifications.updateServiceAlerts

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.

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
serviceId*string

Panel-issued id.

Match^[a-z0-9]{16}$
useDefaults*boolean
rules?array<>
Itemsitems <= 17

Response Body

Success.

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

Update the default alert rules POST

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.

Disable a person POST

Blocks sign-in for an account and ends its sessions and API keys right away. Grants and history stay; users.enable undoes it. Needs `users.manage`, which owners and admins hold. Not available to MCP clients or the assistant.