Edge Web Push

Connect Edge Web Push (VAPID web push for Microsoft Edge) to Push — the form saves, but Norbix cannot send through it yet.

Edge Web Push delivers notifications to Microsoft Edge on the desktop and on Android, through the standard web push protocol. The browser subscribes on your website with your VAPID public key; Norbix signs each message with the matching private key.

Norbix cannot send through Edge Web Push yet. Cloud shows the form and saves the integration, but Test integration and every send answer Push integration 'EdgeWebPushIntegration' is not supported. To try your flows, use Fake Push (Test Me); for real devices use APNs or Firebase. The settings below can already be saved in Cloud or from code.

Get your credentials

1. Make a VAPID key pair once, for example with the web-push package: npx web-push generate-vapid-keys. It prints a Public Key and a Private Key (URL-safe base64).

2. Use the same public key in your website's service worker (pushManager.subscribe({ applicationServerKey })).

3. Pick a contact for the VAPID Subject: an e-mail address as mailto:[e-mail].

Keep the private key on the server side only; never ship it to the browser. Changing the key pair ends every existing browser subscription.

Connect it in Cloud

Where: Push → Integrations → Add New Integration → Edge Web Push → Connect · /projects/<project>/push/integrations/new/edge-web

Field	Required	What it does	Example
VAPID Public Key	yes	The public key your Edge client subscribes with.	BAhUY_6Wz7Lc33txHfOUQ78l…
VAPID Private Key	yes	The matching private key. Encrypted on save and never shown again.	••••••••
VAPID Subject (optional)	no	A contact recorded in the VAPID header. Only an e-mail is accepted, as mailto:….	mailto:[e-mail]
Integration Name	yes	The name in your integrations list.	Acme website (Edge)

The filled form (the keys are made up for the docs).

Press Save. The page turns into Editing Edge Web Push integration with the badges ENABLED, NOT TESTED, NOT CONFIRMED; the private key is not shown again.

After save.

A subject that is a web address is refused, although the form says e-mail or URL:

A URL subject is refused; use mailto:.

Test and set as default

Test integration answers Push integration 'EdgeWebPushIntegration' is not supported, so setting it as default has no use yet. See Test an integration and Set an integration as default for the flow.

Common errors

Message	Cause	Fix
Push integration 'EdgeWebPushIntegration' is not supported	Every send or test today.	Use Fake Push (Test Me), APNs or Firebase.
Property Subject creation failed … is invalid (CM-ERRORS-PROPERTY-002)	A subject that is not an e-mail, e.g. https://acme.example.	Use mailto:[e-mail], or leave it empty.
Required	An empty field — on edit also the private key.	Fill every field, type the private key again.