Each application gets its own API keys, credentials, subscribers, and notification history.
Active subscribers
Delivered
Across all campaigns
Failed
Includes invalid tokens
Clicks
Tracked by the web SDK
Recent notifications
The latest campaigns for this application
| Notification | Audience | Status | Sent | Failed | Clicks | Created |
|---|---|---|---|---|---|---|
Compose a notification
Queue it now or schedule it for later. Delivery starts within a few seconds.
Live preview
now
History & logs
Every campaign, delivery count, and per-subscriber result.
| Notification | Audience | Status | Sent | Failed | Clicks | Created | Logs |
|---|---|---|---|---|---|---|---|
Subscribers
Devices and browsers registered for this application.
| Subscriber | Platform | External user ID | Tags | Status | Last seen | Actions |
|---|---|---|---|---|---|---|
|
—
|
|
No subscribers found
Install the web SDK or register a mobile token to get started.
Firebase Cloud Messaging
Android delivery using a Firebase service account.
Project:
Apple Push Notification service
iOS delivery using a .p8 auth key.
Web Push (VAPID)
Browser subscriptions use these keys. Changing them invalidates existing subscriptions.
Use a mailto: address or an https:// URL.
Public key
Generating a new key pair replaces the current one.
Web SDK snippet
Drop this into any page. Host the service worker at your site root as pushforge-sw.js.
Backend API snippet
Send from your server with the REST API key.
Application keys
The public key identifies the app in clients. The REST key authorizes server-side sends.