OneSignal

OneSignal is a push-notification service built for scale. On top of plain "send a message to a device," it adds audience segmentation, A/B testing, scheduled and automated sends, and delivery analytics so you can see what landed and what converted. Connect it when you want to run real notification campaigns from an app you build with Appsanic, not just fire the occasional alert.

If all you need is to receive push with nothing extra to set up, you don't need OneSignal at all - see Push Notifications and Expo Push.

What you get by connecting it

Once OneSignal is connected, the agent can:

Wire the OneSignal device SDK into your app using your App ID, so each install registers as a subscriber.
Send notifications from your backend through OneSignal's REST API, routed via a server-side relay that holds the secret send key.
Build features that lean on OneSignal's segmentation and A/B testing, and read its delivery analytics for sent, delivered, and opened counts.

Connecting it

OneSignal uses two credentials:

An App ID - the public identifier for your OneSignal app, safe to embed in the device SDK.
A REST API key - a secret send key beginning with os_v2_app_... that authorises sending.

Find both in the OneSignal dashboard under Settings then Keys & IDs.

Paste both into Dashboard then Connectors then OneSignal. Connect once and every project in your account can use it. (Connecting requires a paid plan.) There is no one-click OAuth for OneSignal - one-click OAuth exists only for Supabase and Stripe.

Saved secrets show as dots - the browser only ever sees that a key exists, never its value. The connector page has a Test connection control to re-check the credentials against the live service, and a Disconnect control to remove them.

Keys and security

OneSignal spans two of Appsanic's credential tiers, because its two credentials behave differently:

The App ID is publishable by design. The agent embeds it directly in the device SDK - there is no relay for this side.
The REST API key is secret. Anyone holding it can send notifications on your behalf, so it must never be bundled into an app people download. The generated app reaches OneSignal's send endpoint through a small server-side relay that holds the key. With Supabase connected, Appsanic can deploy that relay for you as a Supabase Edge Function.

OneSignal does not get an Account access toggle. Account access (where the agent acts inside your account with server-side tools) is offered only for Supabase, Stripe, and Resend.

Managed connector secrets are encrypted at rest with AES-256-GCM. The AI never sees a decrypted secret and will never ask you for a key in chat.

Useful links

OneSignal documentation: https://documentation.onesignal.com
Appsanic guide: Push Notifications

Read Push Notifications for the full picture on reaching users when your app is closed, including when Expo Push is enough and when OneSignal earns its place.

DocsConnectors

4 min readUpdated Jun 29, 2026

OneSignal

If all you need is to receive push with nothing extra to set up, you don't need OneSignal at all - see Push Notifications and Expo Push.

What you get by connecting it

Once OneSignal is connected, the agent can:

Wire the OneSignal device SDK into your app using your App ID, so each install registers as a subscriber.
Send notifications from your backend through OneSignal's REST API, routed via a server-side relay that holds the secret send key.
Build features that lean on OneSignal's segmentation and A/B testing, and read its delivery analytics for sent, delivered, and opened counts.

Connecting it

OneSignal uses two credentials:

An App ID - the public identifier for your OneSignal app, safe to embed in the device SDK.
A REST API key - a secret send key beginning with os_v2_app_... that authorises sending.

Find both in the OneSignal dashboard under Settings then Keys & IDs.

Keys and security

OneSignal spans two of Appsanic's credential tiers, because its two credentials behave differently:

The App ID is publishable by design. The agent embeds it directly in the device SDK - there is no relay for this side.
The REST API key is secret. Anyone holding it can send notifications on your behalf, so it must never be bundled into an app people download. The generated app reaches OneSignal's send endpoint through a small server-side relay that holds the key. With Supabase connected, Appsanic can deploy that relay for you as a Supabase Edge Function.

OneSignal does not get an Account access toggle. Account access (where the agent acts inside your account with server-side tools) is offered only for Supabase, Stripe, and Resend.

Managed connector secrets are encrypted at rest with AES-256-GCM. The AI never sees a decrypted secret and will never ask you for a key in chat.

Useful links

OneSignal documentation: https://documentation.onesignal.com
Appsanic guide: Push Notifications

Read Push Notifications for the full picture on reaching users when your app is closed, including when Expo Push is enough and when OneSignal earns its place.