NotificationHub
NotificationHub is a multi-tenant notification platform. The Java and Node.js SDKs give you a typed client for sending notifications across Email, SMS, Push, Webhook, and In-App channels, managing projects, configuring providers, working with Handlebars-style templates, and reading back delivery analytics — all through one signed HTTP client.
What you can do with the SDK
Send notifications Dispatch a single message to one or more channels with a fluent request builder, or send in bulk. | Manage projects
Create tenants, rotate API keys/secrets, and control project lifecycle status ( |
Configure providers Attach, test, update, and remove the underlying provider credentials for each channel. | Build templates Create reusable templates with a name, subject, and body, and preview them with real variables before sending. |
Track engagement Fetch delivery receipts and open/click tracking data per notification. | Observe your system Pull aggregate metrics, audit logs, and dead-letter-queue entries, and retry failed deliveries. |
SDK support matrix
| Capability | Java SDK | Node.js SDK |
|---|---|---|
| Notifications (send, bulk, search, receipts, tracking) | ✅ | ✅ |
| Templates (CRUD + preview) | ✅ | ✅ |
| Projects (create, list, update, rotate credentials) | ✅ | ✅ |
| Providers (configure, test, update, delete, list) | ✅ | ✅ |
| Analytics (metrics, audit logs, DLQ, retry) | ✅ | ✅ |
| Typed exception hierarchy (auth / validation / rate limit / server) | ✅ | ✅ |
| Spring Boot auto-configuration | ✅ | — |
How requests are authenticated
Every SDK call is signed with HMAC-SHA256 and carries your API key, using the same signing scheme in both SDKs. See Authentication for the full header breakdown and how to keep your secret safe.
Where to go next
- New to the SDK? Start with Installation and the Quickstart.
- Want the conceptual model first? Read Notifications, Templates, and Projects.
- Already integrating? Jump straight to the Java API reference or Node.js API reference.