Skip to Content
SeyloDocs
API referenceAlerts

Remove a mute

POST
/api/v1/alerts.unmute

Ends a mute now so its scope notifies again.

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

Authorization

cookieseylo_session<token>

Request Body

application/json
  1. body
muteId*string

Panel-issued id.

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

Response Body

Success.

application/json
  1. response
Example Request
curl -X POST 'https://example.com/api/v1/alerts.unmute' \  -H 'Content-Type: application/json' \  -d '{  "muteId": "string"}'
Example Response
{}

List alert mutes GET

Lists the mutes that are still in effect. Muted alerts still appear in the feed, marked muted, but no channel is notified. Needs `alerts.manage`, which owners and admins hold. Available to MCP clients and the assistant.

Create an API key POST

Creates an API key or MCP token for the signed-in person, limited to the given actions ("*" for all of yours), optionally to some projects, read-only or not, with an optional expiry. The token is returned once. Browser sessions only, signed in or confirmed with auth.reauth in the last 15 minutes (FORBIDDEN details.reason "reauth" otherwise). Any signed-in caller. Not available to MCP clients or the assistant.