Skip to main content
Use Listener alerts to send an immediate notification to listener apps subscribed to a station topic. The station needs a configured push provider and credential, and your role must allow the action.

​
Compose and send

  1. Confirm the active station.
  2. Enter a title and message, then choose the Alerts or Content topic.
  3. Add an optional public HTTP or HTTPS link that listeners can open without signing in.
  4. Choose Review and send, check the station and message, and confirm the send.
Titles can contain up to 200 characters and messages up to 2000, with an overall payload size limit. Emoji and links count toward that limit. Shorten the message if the review reports that it is too large. A sent alert cannot be recalled. Review links and factual content before confirming.

​
Check the outcome

The last-alert area shows timing and delivery outcome. Queued confirms a request is in the delivery queue; it does not prove that every listener device displayed it. Refresh status to check progress. If a send could not be confirmed, retry without changing the message to avoid sending a duplicate. If delivery is unavailable, refresh status and ask an administrator to check the station’s push configuration.

​
Alerts from editorial publication

An editorial record can request Push to listeners when it is published. That route sends to apps subscribed to content and reports its own delivery status. Check publication and notification outcomes separately. Station credentials for listener device registration use push:register. See Integrations for scope and storage guidance.