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 you only need basic Expo Push, see Push Notifications. Either provider still needs native credentials and a development build before remote notifications reach a device.
What you get by connecting it
Once OneSignal is connected, the agent can:
- Generate preview-safe notification UI and commented OneSignal native-SDK setup using the public App ID.
- Generate a narrow server-route contract for OneSignal REST sends.
- Explain how to configure APNs/FCM, install a development build, and use OneSignal's dashboard features after setup.
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.
Open the project build, select Connectors, choose OneSignal, and enter both values. The connection applies only to that project and requires a paid plan. Connector OAuth is not currently available.
The publishable App ID remains visible; the secret REST API key shows as dots and never returns to browser JavaScript. Test now checks that the two values identify the same OneSignal app. It does not prove APNs/FCM credentials, device registration, native SDK setup, or delivery. Use Disconnect to remove the values from the project.
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 preview can reference it, but the native SDK remains commented setup until you install it and make a development build.
- 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. Use a separately deployed server-side relay and put a dedicated key in that runtime's secret manager. The agent can generate a Supabase Edge Function or another backend, but the saved connector key is not transferred into it.
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 model prompt never receives a decrypted secret, and the agent will never ask you for a key in chat.
Useful links
- OneSignal documentation: https://documentation.onesignal.com
- Appsanic guide: Push Notifications
Next
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.