List your alert destinations

Your destinations, primary first.

• kind is email or telegram (push_device is reserved for the mobile apps).
• target is your email address for email, or the linked chat's id for telegram.
• classes lists the alert classes routed here, is null for every class, or is [] for none (the destination is kept but receives nothing).
• is_primary marks the destination of your linked Telegram chat. It is derived from the link, never set through this API.

Until you write a destination, you are on the default: every class goes to your linked Telegram chat when there is one, and email carries what nothing else does. The list is empty while the default applies, and the grid in the app shows the default as every cell ticked on the chat. Linking Telegram writes the default down as rows, so from then on the rows lead.

Critical classes always reach your email. Security notices, an open Sev1 or Sev2 incident and an exhausted AI budget are sent to your email whatever the destinations say, because they arrive when the chat you would otherwise read them on may be the thing that failed. Routing them to Telegram adds a message there; it never removes the email.