Mobsted provides Push capabilities to both Android and iOS users. Each user can make a choice of how to accept Push. In a Still way, how Push is delivered are different.
The panel below shows how to send
The difference here is that iOS devices are incapable of sending Push into browser, which is compensated by a choice of mobile messengers. Android
Getting User Permissions to send Push
First. You need to set IDs of users accessing your app.
This creates Push addresses within your app for each user.
Mobsted will add this address to each new or existing user entering the app container, if you pass a UTM with your internal user ID to the app's link with еру &utm_extid command:
xxxxxxxxx.mobsted.com/pwa/?appid=NN&utm_extid=some-alphanumeric-ID
This becomes an external ID of your user for Mobsted.
PLEASE - do not use anything related to personal data, like phone numbers, emails, or names. The best way is to use some hashed or random aplahnumeric ID, like - jhFd2kjhDc-29dkY35-Kf93gh4skJ and so on.
NOTE - This field is case sensitive, so "F1g" is not the same as "f1g"
NOTE - This field is case sensitive, so "F1g" is NOT THE SAME as "f1g", so you need to address your users with exactly the same ID as you've created it with.
Second. You need to setup Push request widgets.
which will record the permission, which channel each user chooses and
Sending Messages through multichannel Push API
To address any of your users, who gave permission to receive Push notification you only need one API method:
POST https://ppp-admin.mbst.xyz/api/v8/object/sendpush
{
"applicationId": 1,
"extId": "100500",
"title": "Hello",
"message": "It`s message about your order#"
}
Where:
"applicationId" - is the same ID which you see in your long links
"extId" - is any alphanumeric ID, which you pass to the app, when sending your users to it with their IDs
"title" - what will be visible as a header in Push
"message" - your text with a name, links and any other info needed
NOTE - we do not support bulk Push to make sure that users only get relevant content and are not bombarded with loads of mobile messages.
For authenticating your sending party you can use static basic auth keys, which you can find here:
Or dynamic JWT keys, which you can find here:
Step-by-step guide
Related articles