Skip to Content
SeyloDocs
API referenceNotifications

Send a test notification

POST
/api/v1/notifications.testChannel

Sends a test message. Pass channelId to test a saved channel, config to test unsaved settings, or both to test edits (secrets left out come from the saved channel).

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
channelId?string

Panel-issued id.

Match^[a-z0-9]{16}$
config?|||||||

Response Body

Success.

application/json
  1. response
ok*boolean
error*string|null
durationMs*integer
Range0 <= value
Example Request
curl -X POST 'https://example.com/api/v1/notifications.testChannel' \  -H 'Content-Type: application/json' \  -d '{}'
Example Response
{  "ok": true,  "error": "string",  "durationMs": 0}

Get a service's alert rules GET

Returns whether a service uses the default alert rules or its own, the rules in effect and the defaults for comparison. Only service events (serviceAlertEvents) apply here. Needs `services.view` on the service (a grant on its project covers it). Available to MCP clients and the assistant.

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.