board Public API · Alert channel subscriptions are not marked as actionable

Support confirmed that the subscriber count in the UI accounts for group alert overrides, while GET /v1/alert-channels returns every subscription in the database regardless of whether it would ever be actioned. In their words, those subscriptions "may or may not be actioned when an alert is fired, as these do not account for group override settings."

That means the API cannot answer the only question a monitoring-as-code setup needs to ask: for this check, which channels would actually be notified right now? On our account the UI reads 14 of 14 checks, 0 of 1 group while the API returns 30 subscriptions for the same channel, and both are correct under their own definitions.

Request: either an actionable boolean on each returned subscription, or a resolved endpoint such as GET /v1/checks/{id}/effective-alert-channels. Without one, a CLI-managed account can only verify what it stored, not what would be delivered — and those differ exactly when a group override is in play.