NovaBell developer guide¶
NovaBell is the platform notification service. A first-party service publishes a notification once; NovaBell renders it, delivers the email, and stores the in-app copy that the signed-in user reads in Notification Center.
NovaBell is not offered as an external developer API through the public API edge. The surfaces below are the contract between NovaBell and the first-party services and console clients that already run inside the platform.
Two surfaces, two callers¶
Publisher surface — a service triggers a notification with its own workload token. The publisher owns the event and the destination it links to; NovaBell owns rendering, delivery, and the stored copy.
Console surface — the browser reads the signed-in human’s own feed with that person’s bearer token and their current Account or Organization context. The console client never holds a publisher credential.
Treat delivery as asynchronous. A publisher must not make its primary transaction depend on an email provider’s response: a notification that could not be delivered is a delivery problem, never a reason to fail the business operation that produced it.