Frontend shared concepts
All Notifizz frontend SDKs (React, Angular, Vanilla JS) share the same underlying widget and expose the same capabilities through framework-idiomatic APIs. This page covers the concepts that apply across all of them.Widget lifecycle
Every frontend SDK follows the same lifecycle:- Load — The SDK injects the Notifizz widget script into the page.
- Authenticate — The widget authenticates the user based on your
authTypeconfiguration. - Ready — The widget signals it is ready to display notifications. The
isReadystate becomestrue. - Active — The widget listens for real-time updates and keeps the notification list current.
- Destroy (optional) — The widget is removed from the DOM and all listeners are cleaned up.
Positioning
Control where the bell icon appears using theposition option:
Styling
Fine-tune the placement of the bell and the notification center with style options:Bell styles
Notification Center styles
State model
All SDKs expose the sameNotifizzState object:
How to access state
- React
- Angular
- Vanilla JS
Programmatic control
All SDKs let you open, close, and toggle the notification center programmatically:
This is useful for triggering the notification center from a custom button, a keyboard shortcut, or an in-app event.
Custom bell
Every SDK supports replacing the default bell icon with your own UI element. The approach varies by framework:- React —
renderBellprop with a render function receivingNotifizzBellContext. - Angular — Content projection via
ng-contentwith a#customBellIcontemplate reference. - Vanilla JS —
setBellElement()method that attaches click handling and unread data attributes.
Default URLs
The widget connects to these endpoints by default:
You should not need to change these unless instructed by Notifizz support.
Authentication options
All frontend SDKs accept the same authentication fields:
See Authentication for a full guide on choosing the right strategy.
Next steps
React SDK
Full API reference
Angular SDK
Full API reference
Vanilla JS SDK
Full API reference