Sosyabot Docs

English

Türkçe

English

Türkçe

Appearance

Notifications ​

Notifications are short alerts from Sosyabot that tell you when something happened, like a post going live, a post failing, or an account that needs to be reconnected.

Why it matters ​

You don't have to keep checking the app to know if things are working. Sosyabot tells you the moment a post publishes, a post fails, or one of your social accounts stops working so you can fix it.

Step by step ​

Open your notifications

Look for the bell icon in the top bar and click it. A list of your latest alerts opens.

Read an alert

Each alert is one short line, like "Your post was published" or "Reconnect your account." Click an alert to jump straight to the thing it's about.

Mark them as read

Click an alert to mark it read, or use "Mark all as read" to clear the whole list at once.

Choose how you get them

Want fewer pings, or alerts by email too? Open Preferences to turn each kind of alert on or off.

TIP

If an alert says an account needs reconnecting, click it and follow the prompts. Posts can't go out on a disconnected account.

Good to know ​

  • Alerts can reach you inside the app, by email, and by push on supported devices.
  • Some alerts come from Sosyabot automatically (like a failed post), and some are messages sent to you by an admin.
  • You decide which alerts you receive and where, on the Preferences page.

Preferences

Channels

Core concepts

For developers

Notifications are stored per recipient and served through these endpoints:

GET  /api/v1/notifications              list
POST /api/v1/notifications/:id/read     mark single read
POST /api/v1/notifications/read-all     mark every notification read

Each record carries a recipient_id (indexed for inbox queries), a source of "auto" (system) or "manual" (admin broadcast), a type, an optional message, an optional url deep link, and a read_at timestamp. Delivery fans out across in-app, email, and push based on the user's per-event toggles in Preferences.