The tokens are an important part of this API since it identifies each (user) actor (device and applications) in a unique or shared way.
This token identifies the user or group of users and on extended API SHALL be a secret but in simple push API (thialfi like) it's not needed to be a secret.
If this token is UNIQUE (and secret, of course) will identify a unique instance of the application related (normally) to one user. In this case the returned URL will be unique for this channelID. On simple push, each device with same channelID will receive a unique endpointURL.
If this token is shared by different devices of the SAME user (and secret), will identify a unique user with multiple devices. In this case, the returned URL will be unique per user but each URL will identify multiple devices the user is using.
Example 3.1. Multiple device messages
This can be used by applications in which the user require the same information across his devices, like the mobile and the desktop app. Can be used, for example, by e-mail clients.
Finally, if a developer decides to deliver the same WAToken to all his users (in this cases is obviously not a secret one), then the returned URL will identify all instances of the same application. In this case each notification received in the publicURL will be delivered to ALL the devices which have the application installed (and registered). This will be a BROADCAST message.
Example 3.2. Message broadcast
This can be used by applications in which all users require exactly the same information at the same time, like weather applications, latest news, ...
This token identifies each customer device in a unique way.
This token is also used as an identification key since this isn't a random one. This token is an AES encrypted string which will be checked for validaty each time it's used.