Docs / Reference / act: notification rule

act: notification rule.

Writes one notification rule, which says who is told and never what happens to The answer gives the rule, with the next notice it will send

Figure 1POST /v1/act/notification_rulespecified

The caller sends NotificationRuleInput to /v1/act/notification_rule. The platform returns a card whose body is NotificationRule.

POST/v1/act/notification_rule

Write a notification rule. The call needs the user rung under a token with the act grant, and it is served by the platform.

The route takes NotificationRuleInput and returns a card whose body is NotificationRule.

Request body#

The request body is NotificationRuleInput.

field	type	required
`name`	`text`	yes
`notices`	`[text]`	yes
`channel`	NotificationChannel	yes
`quiet_hours`	`text`	no
`digest`	`one of none \| hourly \| daily`	yes

Response#

The route returns a card whose body is NotificationRule. Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true.

Headers#

header	required	meaning
`Scale-Scope`	yes	the scope the call runs in: tenant/, then /brand/, then /strategy/
`Scale-As-True-On`	no	the date the facts must have been true on; defaults to now
`Scale-As-Known-On`	no	the date the facts must have been known on; defaults to now
`Scale-Key`	no	for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing

A caller needs the user rung and a token with the act grant. The platform serves this route.

Example#

The example sends the smallest body that NotificationRuleInput allows. The build validates it against the schema of NotificationRuleInput.

Example

curl -X POST https://api.scaleintelligence.co/v1/act/notification_rule \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "name": "…", "notices": [], "channel": "…", "digest": "none" }'

import { client } from "@scale/sdk";
const answer = await client.act.notification_rule({
    "name": "…",
    "notices": [],
    "channel": "…",
    "digest": "none"
  });
// answer.body is a NotificationRule. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/notification_rule",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "name": "…",
      "notices": [],
      "channel": "…",
      "digest": "none"
    }).json()

let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/notification_rule")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&NotificationRuleInput { /* the fields of the page */ }).send().await?.json().await?;

MCP tool#

The MCP tool si.act.notification_rule takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from ui://scale-intelligence/cards/NotificationRule. The tool’s page describes it.

POST /v1/act/notification_rule
Scale-Scope: …
Scale-As-True-On: …
Scale-As-Known-On: …
Scale-Key: …
content-type: application/json

{
  "name": "…",
  "notices": [],
  "channel": "…",
  "digest": "none"
}

Without a key, this page shows the request only. The request body is NotificationRuleInput, and the route returns a card whose body is NotificationRule.

Claims#

claim	state	route or tool
The platform serves the route /v1/act/notification_rule at contract 0476e35e6e275db5.	target	`/v1/act/notification_rule`