Onesignal as a REST API

Mobile Beta
1

Please tell me how to use the onesignal as a REST API in a mobile app.

2

oneSignal doesn’t work as a pure REST-only solution for mobile apps. the REST API is only for sending notifications, not for registering devices.

in a mobile app, the device has to be registered through the oneSignal SDK first (ios or android). that’s what creates the subscription and generates the player_id / subscription_id. once that exists, you can use the REST API from your backend (or bubble) to send notifications to that device.

so the flow is: SDK runs on the device → device gets registered in oneSignal → you store the player id in your database → you use the REST API to send notifications to that id. without the SDK step, oneSignal can’t send pushes to a mobile app.

3

So you can’t use the OneSignal SDK in Bubble’s mobile app, right?

4

exactly, you can’t run the OneSignal SDK directly in Bubble’s native mobile app. bubble doesn’t let you inject the SDK in a way that can register devices, so you can’t generate player_ids or use custom sounds there.

the only thing you can do in Bubble Mobile is use the built-in push notifications, which are limited to the device’s default sound. OneSignal with custom sounds only works on web apps or PWAs where the SDK can actually run.