Features · Any Website
Push notifications on any site you control.
A custom build, a static site, a framework nobody has heard of — if you can add a script tag and a file at your web root, you can collect subscribers and send to them, with the same segmentation, automation and analytics behind it.
Three steps, no app store
Nothing to review, nothing to approve, and no platform sitting between you and your subscribers.
Add your site, get a key
Create the site in your NotifyPress dashboard and copy its public site key. That key identifies the site to the widget and is safe to put in your page source.
Add two files
A script tag with your site key, and a one-line service worker at your domain root. Both are copy-paste from your site settings — the root file is the only real requirement, and it is what the browser insists on.
Send from anywhere
Compose from the dashboard like everyone else, or drive it from your own backend over the REST API — the same API the WordPress plugin uses, with nothing held back for it.
One requirement worth checking first
Browser push needs a service worker served from the root of your domain, over HTTPS. That is a rule of the web platform, not ours, and it applies to every push provider equally — so the question that decides whether any of this will work on your platform is simply: can you put a file at /service-worker.js?
On your own hosting, a static host, or most site builders, yes. On some closed platforms, no — and we would rather you found that out on this page than after signing up.
What the API gives you
Authenticated with a per-site token, so a key you give one project cannot touch another.
Send, schedule, cancel
Fire a campaign from your own code, queue one for later, or cancel one already going out. Everything you can do in the composer has an endpoint behind it.
Tag and segment
Tag a subscriber by token when something happens on your site, create and preview segments, and check how many people a rule matches before you commit to it.
Trigger automations
Post an event name and a subscriber token to start a workflow — a completed purchase, a finished trial, whatever your backend already knows about.
A spec you can generate from
The whole API is published as a machine-readable OpenAPI description, so a client library or an agent can read it directly rather than working from prose.
On WordPress instead?
Then skip all of this. The plugin connects in a click, installs the widget, serves the service worker for you, and adds publishing and WooCommerce features that the generic snippet does not have.
Questions, answered.
Paste a snippet, get subscribers.
Free forever for up to 300 subscribers. No credit card required.