Creator Notify v1.0.0

Creator Notify

A browser push notification API. Create an account, copy two keys, collect browser subscriptions with a small JavaScript SDK, and publish notifications from your own admin panel with a single REST call.

Get your keys Two keys, one website, about ten seconds. Send one now The demo delivers a real notification to this browser. Check status Service health, lifecycle and delivery, drawn as a page. API reference Every endpoint, field and error code.

Start here

Create an account to get your keys in about ten seconds, then open the demo and send yourself a real notification. No email, no dashboard to set up.

What Creator Notify is (and is not)

It isIt is not
A REST API you call from your own backend A hosted dashboard you have to log into every day
Multi-tenant: many independent websites share one service A single-site script with hard-coded credentials
Web Push (VAPID) — the W3C standard browsers already implement A proprietary delivery channel or a browser extension
At-least-once submission to the push service, with per-attempt records A guarantee that a human saw the notification
Language-agnostic: PHP, Node, Python, Go, cURL Tied to any particular frontend framework

How browser push notifications work

Every modern browser ships a push service (Chrome and Edge use FCM, Firefox uses Mozilla autopush, Safari uses Apple Push Notification service). Your page asks that service for a PushSubscription, which is an HTTPS endpoint plus two keys. When you send an encrypted message to that endpoint with a VAPID-authorised request, the push service wakes the browser and your Service Worker renders the notification. Nobody — including Creator Notify — can read the subscriber's identity or the message contents in transit.

1
Your page collects a subscription

The Service Worker is registered, permission is requested after a click, and pushManager.subscribe() returns an endpoint.

2
The SDK uploads it

POST /v1/subscriptions with your public key. Nothing secret leaves the browser.

3
Your backend publishes

POST /v1/notifications with your secret key. The API encrypts the payload per RFC 8291, signs a VAPID JWT (RFC 8292) and issues one HTTPS request per subscription.

4
The push service answers

201 accepted, 404/410 gone, or an error. Creator Notify records the outcome for every subscription.

Delivery semantics

What the numbers mean

A push service acknowledging a message means it accepted it for delivery. The device may be offline, the user may have muted the site, or the OS may drop the notification. Creator Notify never reports "delivered" or "read" — only whether the push service accepted, rejected or invalidated each subscription.

Requirements

  • An account on this service — create one here. You get two keys: a public key and a secret key.
  • A domain served over HTTPS for your website (push requires a secure context; localhost also works while developing).
  • Server-side code (PHP, Node, Python…) where your secret key can live. Never in the browser.

The ten-minute path

1
Get your keys

Create an account — the public key goes in your HTML, the secret key stays on your server. → API keys

2
Try it immediately

Open the demo, paste the secret key, allow notifications, type a message and send. → Quick start

3
Integrate the SDK

Host creator-notify.js and service-worker.js on your site and add an "Enable notifications" button. → Integration guides

4
Send

Call POST /v1/notifications from your backend every seven days at minimum. → Notification guide

Prefer to run it yourself?

The API is open source under the MIT licence and can be self-hosted; the repository's README contains the operator instructions. Everything on this site works the same way against your own instance — only the API address changes.

API conventions

  • Base path: /v1 for everything except GET /health.
  • Auth: Authorization: Bearer <secret key> on every management endpoint.
  • Content type: application/json both ways.
  • Timestamps: ISO-8601 in UTC, e.g. 2026-01-31T12:00:00.000Z.
  • Envelope: {"success": true, ...} or {"success": false, "error": {"code", "message", "details"}}.
  • Request id: every response carries an x-request-id header; include it in bug reports.

Next