Skip to main content
← Data, API & Backend
Data, API & Backend October 16, 2022 · 4 replies

OneSignal API Requests (Player ID)

Archived from the Bravo community forum (2021–2026). Some answers may refer to older versions of Bravo.

In order to send user-specific API requests to OneSignal, I need access to the Player ID. Is this available in Bravo?

I'm trying to add tags to the OneSignal user through a form in my Bravo app, so I can target my push notifications. Edit device (onesignal.com)

Thanks

4 replies

Valter October 16, 2022

You already have tags on subscribed users, as the deviceId, userId and email. Just use one of those tags in you POS json body filter to send a push just to to that user.

Jerry October 16, 2022

I want users to be able to opt into priority notifications or all notifications.

I could maintain a separate database of which users signed up for which push notifications, but then I’d have to call OneSignals API for every single user. I’d rather have a priority tag in OneSignal so I only call them once & they deal with the dispatching.

Valter October 16, 2022

Guess you cant do it. The only solutoon its users sending that info to your backend and you later manualy change at onesignal.

Diego Iglesias Bravo team October 24, 2022

You should use the user id instead of the playerID. You will need to add authentication to your app in order to get this parameter.

Once the user signs up and enables notifications, the OneSignal registry will include user id along with the device id.

By the way, if you are using Xano you can add this snippet to your endpoint to send notifications from there https://www.xano.com/snippet/wU7QiMUz/

Wrote something in this thread and want it removed? Request removal

Still stuck?

Ask the community on Discord

This archive is read-only. New questions, office hours and product updates now happen in the Bravo Discord.

Join the Discord