Notifications
Overview
Push notifications: device register/list/delete, send, templates, and delivery history.
API
{pe} = /projects/{projectId}/environments/{environmentId}.
| Method | Path | Notes |
|---|---|---|
| GET | /notifications/health | Health |
| POST | /notifications{pe}/devices | API key scope notifications:register |
| DELETE | /notifications{pe}/devices/{*token} | Register scope or JWT |
| POST | /notifications{pe}/send | Full scope or owner JWT |
| GET | /notifications{pe}/devices | Console JWT |
| GET/POST | /notifications{pe}/templates | Console JWT |
| PUT/DELETE | /notifications{pe}/templates/{templateId} | Console JWT |
| GET | /notifications{pe}/deliveries | Console JWT |
Clients
| Package | Runtime |
|---|---|
@vijihub/notifications | server (send) |
@vijihub/notifications-web | browser (register) |
VijiHub.Notifications | .NET |
Implementation
- Enable Notifications and configure the push provider.
- Register devices from the client with
@vijihub/notifications-weband a scoped register key. - Send notifications from your backend with a full key or JWT.
- Manage templates and inspect deliveries in Console or via JWT APIs.
Constraints
- Browser clients may only use
notifications:register— never full send keys. - Send requires full API key scope or owner JWT.
- Template/delivery admin is Console-authenticated.