API documentation

Alerts by email

Stonewake can send you an email when an alert on your team's book reaches the severity you choose. This page explains how you turn it on, what a mail says, which alerts reach you, the limits, and how every delivery is recorded. You turn it on in the dashboard. The API and MCP read the delivery record and never an address.

Turning it on

Open Settings in the dashboard. The card Email alerts sends your alerts to the address your sign in states. Switch it on, choose the lowest severity that reaches you, critical only, high and critical, or every severity, and save. The setting is yours alone. It covers every alert class your team holds and changes nobody else's alerts. Switching it off stops the alert mail to you at once. When your sign in carries no email address, no alert mail can reach you, and the card says so. An API key never receives alert mail.

What a mail says

A mail is written in your workspace's alert language. A German alert mail carries the English text below the German one; an English alert mail is English only. The subject starts with Stonewake and names the severity and, where it is known, the company. The mail names the company where it is known, what changed, the date the source states and the source itself, so every claim carries its provenance, and it links to the dashboard. Dates are calendar days on your workspace's clock, German time unless an administrator of your workspace chose UK time.

Which alerts reach you

An alert reaches you by email when it belongs to your team or to the whole workspace, its severity is at least the one you chose, you are an active member of the team, and your team holds the part of Stonewake the alert comes from. A news event reaches the teams whose book or watch list holds its company (News monitoring). A fact that was already old when its alert was written is recorded for the daily summary and is not sent. Your workspace administration can also arrange alert mail for a team's members together with Stonewake; those alerts arrive the same way.

Limits

Each workspace has a monthly budget for alert mail and a monthly number of deliveries on each channel, and the mail provider's own monthly allowance applies as well. A mail over a limit is held and recorded, and it is never sent another way. An address that bounced or reported a mail as spam receives no further alert mail. While no limits are set for a workspace, alert mail cannot reach it yet, the card says so, and your setting is kept for when it can. Mail is sent through a mail provider in the EU. In a demonstration workspace no mail leaves Stonewake.

The delivery record

Every mail leaves a record. Each attempt is recorded as queued, sent, failed, or held with its reason. You see your own record on the card. GET /v1/alerts/deliveries with channel set to email and the MCP tool alert_deliveries read the workspace's record by alert, with ids only, never a recipient or an address.