iblai-api-notificationlisted

# iblai-api-notification Read and send an organization's platform notifications via the API: the unread count, the notifications list with channel/status/tag filters, mark-as-read (all, bulk, or specific), delete, and the two-step notification builder (preview then send/schedule, with source validation and recipient preview). Also manage a user's notification preferences, per-user push-device (FCM) tokens and, for org admins, the email templates and SMTP config that back notifications. ## Auth & conventions - **Base URL:** `https://api.iblai.app` - **Header:** `Authorization: Api-Token $IBLAI_API_KEY` on every request. - **Path vars:** `{org}` = `$IBLAI_ORG`, `{username}` = `$IBLAI_USERNAME`, `{platform_key}` = the org/platform key (usually `$IBLAI_ORG`), `{type}` = a notification-type key (e.g. `USER_NOTIF_COURSE_ENROLLMENT`), `{build_id}` = the id returned by the builder's `preview/` step. - These are **platform-level** endpoints on the DM host; all paths below sit under `https://api.iblai.app/dm/api/notification/v1/` (written `…` in this doc). - Not connected yet? Run **`/iblai-api-login`** first to populate `IBLAI_ORG`, `IBLAI_USERNAME`, and `IBLAI_API_KEY`. ## Concepts - **Two-step builder.** Sending a custom notification is `preview/` → `send/`. `preview/` resolves recipients and returns a `build_id`; `send/` takes that `build_id` to actually send (or schedule, when `preview/` was given a `process_on` datetime). `validate_source/` and `{build_id}/re