Reference

Count alerts

Unseen alert counts by severity (pure read).

View MarkdownThis page is generated from the source code on every release.

Unseen alert counts by severity (pure read).

Overview

Name	Value
Code	`alerts.summary`
Scope needed	`audit.read`
Risk	Read
May need confirmation	No
Runs as	Answers right away
Needs `Idempotency-Key`	No
Member roles allowed	`owner`, `manager`, `agent`, `viewer`
In the app	Alert bell

Input fields

This operation takes no fields.

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/alerts.summary \
  -H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Output fields (`data`)

Field	Type	Required
`unseen`	`object`	Yes
`open`	`number`	Yes

Example answer

{
  "data": {
    "unseen": {
      "urgent": 1,
      "attention": 1,
      "info": 1
    },
    "open": 1
  }
}

Using it over MCP

Tool alerts_summary is listed on the profiles: Reports (reports). On other profiles, find it with tools_search and run it with tools_run.

Count alerts

#Overview

#Input fields

#Example request

#Output fields (data)

#Example answer