Docs / Reference / view: waiting

view: waiting.

The caller to notifications, oldest first.

Figure 1POST /v1/view/waitingspecified

The caller sends WaitingInput to /v1/view/waiting. The platform returns a card whose body is [Notification].

POST/v1/view/waiting

What needs me. Acknowledge; what waits for a person. The call needs the user rung under a token with the read grant, and it is served by the platform.

The route takes WaitingInput and returns a card whose body is Notification.

Request body#

The request body is WaitingInput.

field	type	required	note
`acknowledge`	`id`	no

Response#

The route returns a card whose body is Notification. 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 read grant. The platform serves this route.

Example#

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

Example

curl -X POST https://api.scaleintelligence.co/v1/view/waiting \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{}'

import { client } from "@scale/sdk";
const answer = await client.view.waiting({});
// answer.body is a [Notification]. answer.foot holds the basis, the scope and the time.

import requests
answer = requests.post("https://api.scaleintelligence.co/v1/view/waiting",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={}).json()

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

MCP tool#

The MCP tool si.view.waiting takes the same input and returns the same card. The tool only reads data. An MCP host that renders cards draws this card from ui://scale-intelligence/cards/Notification. The tool’s page describes it.

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

{}

Without a key, this page shows the request only. The request body is WaitingInput, and the route returns a card whose body is [Notification].

Claims#

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