Angular Setup

The Angular OneSignal Plugin is a JavaScript module that can be used to easily include OneSignal code in a website that uses Angular for its front-end codebase.


If you have not done so already, you may benefit from following our Web Push Quickstart first.



yarn add onesignal-ngx


npm install --save onesignal-ngx

Library setup

Initialize OneSignal with your appId via the options parameter:

import { OneSignal } from 'onesignal-ngx';

  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
export class AppComponent {
  title = 'angular-example-app';

  constructor(private oneSignal: OneSignal) {
      appId: "8e7fe838-fbcd-4152-980d-32565a2dcf03",

The init function returns a promise that resolves when OneSignal is loaded.

await this.oneSignal.init({ appId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' });
// do other stuff

this.oneSignal.init({ appId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' }).then(() => {
  // do other stuff

Init Options

You can pass other options to the init function. Use these options to configure personalized prompt options, auto-resubscribe, and more (full list of initialization options).

Service Worker Params

You can customize the location and filenames of service worker assets. You are also able to specify the specific scope that your service worker should control. You can read more here.

In this distribution, you can specify the parameters via the following:

serviceWorkerParamUse to specify the scope service worker has control of.
Recommendation: A non-root path that you will never host pages from.

- This prevents conflicts other Service Workers.
Example: { scope: "/onesignal" }
serviceWorkerPathThe path and file to your service worker file with OneSignal included.
Example: "/myPath/OneSignalSDKWorker.js"
   appId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx',
   serviceWorkerParam: {
     scope: '<path scope>'
   serviceWorkerPath: '<path>'

Service Worker File

If you haven't done so already, you will need to add the OneSignal Service Worker file to your site (learn more).

The OneSignal SDK file must be publicly accessible. You can put it in your top-level root or a subdirectory. However, if you are placing the file not on top-level root make sure to specify the path via the service worker params in the init options (see section above).

Visit https://{}/OneSignalSDKWorker.js in the address bar to make sure the files are being served successfully as javascript content. (Consider serviceWorkerParam if you customized it)

If you uploaded the file but you cannot access it via your browser search bar, make sure you have told Angular about it via the assets param in your angular.json file.

OneSignal API


This package includes Typescript support.

class OneSignal {
	Slidedown: IOneSignalSlidedown;
	Notifications: IOneSignalNotifications;
	Session: IOneSignalSession;
	User: IOneSignalUser;
	Debug: IOneSignalDebug;
	login(externalId: string, jwtToken?: string): Promise<void>;
	logout(): Promise<void>;
	init(options: IInitObject): Promise<void>;
	setConsentGiven(consent: boolean): Promise<void>;
	setConsentRequired(requiresConsent: boolean): Promise<void>;

OneSignal API

See the official OneSignal WebSDK reference for information on all available SDK functions.


Service Worker Issues

Check the serviceWorker flag

In your angular.json, see if the serviceWorker flag is set to true. The flag is used to cause the production build to include some extra service worker files that will conflict with the OneSignal worker if they use the same scope. If your web app depends on this flag being true and hence the Angular service worker (ngsw-worker.js) like in PWA setups, you should customize your OneSignal service worker integration to use a different scope than the Angular service worker. Otherwise, they will conflict. This can be done using the service worker OneSignal initialization params documented above. Click for further details.