Skip to main content
Read and send internal notifications.

tai notifications list

List the internal notifications, newest-first. Example: tai notifications list

tai notifications notify

Send a human a one-way, fire-and-forget notification. The rich-send forms are JSON strings validated into their contract models before the request — a list of MediaItem for --media, a discriminated Option list (reply/link) for --options, an OptionSection list for --sections, a ChannelTemplate for --template, a LocationElement for --location, a MediaItem for --header, a JSON object for --schema, a FormData for --data, a FormPage list for --pages and a Wording for --wording — so a mis-shaped value (including an unknown template/location/header/data/wording key, which the contract would otherwise silently drop) raises loudly here. The contract’s cross-field rules (caps, non-blank, the options-XOR-sections choice surface, header/footer requiring a choice surface, template exclusivity, the channel-deliverable form subset, the form data/pages requiring a schema and matching its properties, and each wording member admitted only on the surface that draws it) are enforced by the server. Example: tai notifications notify "Deploy finished" --channel telegram