Notifications
Notification center and bell: bot events, unread counter, announcements.
Sur cette page
GetMyBot keeps you informed about important events across your bots through the notification center: the bell icon in the top bar. It collects both bot events (broadcast completed, payment received, low balance) and platform-wide announcements. The notification feed is tied to your account and is visible across all bots.
Bell and counter
The top bar shows a bell icon with an unread counter. The counter is fetched with a separate lightweight request (GET /api/notifications/unread-count) and updates as new events arrive. Clicking the bell opens the feed.
Notification feed
The feed (GET /api/notifications) combines two sources:
- Notifications: events for your bots and account.
- Announcements: platform-wide messages for all users.
Each item has a title, body text, an optional bot reference (for bot events), a timestamp, and a "read" flag.
Event types
- Broadcast done (
broadcast_done): a mass send has finished. - Payment succeeded (
payment_succeeded): a balance top-up has been confirmed. - Subscription renewed (
subscription_renewed): a plan has been renewed. - Low balance (
balance_low): the request balance is running low. - Bot error (
bot_error): the bot encountered a problem. - New subscribers (
new_subscribers): the bot gained new audience members. - Bot offline (
bot_offline): the bot has had no heartbeat for longer than the threshold in the "Bot health" card; the text names the cause and what to do about it. The bot's owner gets it, once per incident. - Bot back online (
bot_online): heartbeats are back; the text carries the length of the outage. Only sent to whoever received the "Bot offline" notice.
Marking as read
- Single item:
POST /api/notifications/read(by source and identifier). - All at once:
POST /api/notifications/read-allmarks the entire feed as read and resets the counter.
Not the same as customer notifications
Everything on this page is for you and your team: it is delivered to the dashboard and to the operator mobile apps, keyed to your account. Notifications to your customers are a different system with different storage, different credentials and a different audience: see browser push for website visitors and the customer SDK for your own mobile app. Turning one on has no effect on the other.
What's next
- Broadcasts: the "Broadcast done" event.
- Payments and balance: "Payment succeeded", "Subscription renewed", "Low balance".
- People (CRM): "New subscribers".
- Stats and log: tracking spend and balance.
- Projects and channels: "Bot offline", "Bot back online" and the "Bot health" card.