Authentication
Authentication controls how the Notification Center widget identifies the current user to Notifizz. Choosing the right strategy depends on your existing auth setup and your security requirements.Which strategy should I use?
| Firebase | Backend tokens | No authentication | |
|---|---|---|---|
| Security | High (Firebase-verified) | High (HMAC-verified) | None |
| Backend work | None (use existing Firebase) | Generate token per user | None |
| Required fields | token | token, userId, userEmail | userId, userEmail |
| Best for | Firebase apps | Custom auth systems | Development only |
How authentication fits in
Authentication happens when the Notification Center widget initializes. The widget sends the credentials you provide, and Notifizz verifies them before opening a real-time connection for the user. All Notification Center SDKs (React, Angular, Vanilla JS) accept the same authentication fields:| Option | Type | Required | Description |
|---|---|---|---|
apiKey | string | Always | Your Front API Key from the dashboard. |
authType | 'firebase' | 'backendToken' | 'none' | Always | Authentication strategy. |
token | string | For firebase and backendToken | The auth token. |
userId | string | For backendToken and none | The user’s unique identifier. |
userEmail | string | For backendToken and none | The user’s email address. |
Choose your strategy
Backend tokens
Secure authentication with HMAC tokens generated by your backend. Recommended for production.
Firebase
Authenticate with Firebase ID tokens. Zero backend work if you already use Firebase Auth.
No authentication
Connect with just a user ID. For development and prototyping only.