Reference
Alert rules
Set severity / on-off per alert kind.
View MarkdownThis page is generated from the source code on every release.
Set severity / on-off per alert kind.
Overview
| Name | Value |
|---|---|
| Code | alerts.save_rules |
| Scope needed | integrations.manage |
| Risk | Write |
| May need confirmation | No |
| Runs as | Answers right away |
Needs Idempotency-Key |
No |
| Member roles allowed | owner, manager |
| In the app | Settings → Alerts |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
rules |
object[] |
Yes |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/alerts.save_rules \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"rules":[]}'Output fields (data)
| Field | Type | Required |
|---|---|---|
ok |
true |
Yes |
Example answer
{
"data": {
"ok": true
}
}Using it over MCP
Not listed on any profile: call tools_describe then tools_run with code: "alerts.save_rules". Tool name when listed: alerts_save_rules.