Alerts in a linked chat
A chat or group linked to your account, see Link a company chat, receives the alerts your account produces. Every alert states why it was raised.
This page describes the message a linked chat receives and how it is delivered. The monitoring that watches addresses and raises alerts is not part of the public API yet: there is no endpoint to subscribe an address, and this page does not promise any alert type.
Every alert names its cause
An alert is never a bare risk number. It lists the findings that fired and the source each one rests on, and an alert without a usable cause is not sent at all.
| Part of the message | Content |
|---|---|
| Heading | Alert: and the kind of alert. |
| Address | The network and the address the alert is about. |
| Risk level | The band of the address, when the alert carries one. |
| Why this alert fired | Up to three findings, each with its label and a link to its source. More findings are counted as +N more findings in the full report. |
| Time | When the event happened. |
| View evidence | A link to the evidence for the alert, when there is one. |
The source link follows the same rule as a check: a finding that rests on one of our own labels links to its source document, and a rule-based finding, or one that rests on a third-party data source, links to its methodology page. A third-party data source is never named in an alert.
Who receives it
- Every active link of your account receives the alert: each private chat and each group.
- A private chat gets the message in the language its user chose with
/language; a group gets it in the language of its link. - An alert is sent once per link. If the same alert is produced twice, the chat does not get a duplicate.
Stop alerts
Alerts stop for a chat when it is unlinked: send /unlink in the chat, or revoke the link with DELETE /v1/telegram/links/{link_id}, see Unlink a chat. Removing the bot from a group also stops them until the link is restored, see If a group is removed and added again.