Legacy Mode

You can associate your app users and their devices via the OneSignal Player ID (oneSignalUserId) and then send push notifications to specific devices.

Obtain the oneSignalUserId from the oneSignalInfo object — typically after a successful sign-in — and record it in your database alongside the user's account identifier. This gives you full control: you can send to specific devices, remove devices when users haven't logged in for some time, and support multiple accounts on the same device.

There are two ways to obtain and store the Player ID.

Option 1a: Retrieve via JavaScript on your website

Add JavaScript to a login success page to retrieve the oneSignalInfo object. The OneSignal Player ID is available as oneSignalUserId.

iOS note: On iOS, oneSignalUserId will not be set if the user has declined the push notification permission prompt.

/* Login Page Sample Code */
var gn_oneSignalUserId;

function median_onesignal_info(oneSignalInfo){
  gn_OneSignalUserId = oneSignalInfo.oneSignalUserId;
}

function yourLoginFunction(){
  if(gn_OneSignalUserId){
    $.ajax({
      url: updateUserRecord,
      type: "POST",
      data: {
        yourAppUserId: userId,
        oneSignalUserId: gn_OneSignalUserId
      },
      contentType: "application/json"
    });
  }
}

For more JavaScript examples, see OneSignal Info.

Option 1b: POST directly from the native app

Define an API endpoint URL. The app sends a POST request to that endpoint including the user's push token and OneSignal Player ID, along with any session cookies and complete HTTP headers — which your backend can use to identify the user and match an account.

The POST is sent:

1. When the app registers with OneSignal and push tokens are initially created.
2. When a page matching the configured URL is loaded in the app (such as a login success page).

Testing tip: Use .* or All Pages for your URL pattern while testing until you've confirmed your endpoint is receiving the POST. If you still don't receive it, verify the endpoint with cURL or Postman.