Receive Notifications
Last updated
Last updated
© 2023 MOOST AG
MOOST delivers the generated notifications to a REST Endpoint which can be specified by you ("Customer"). You can then deliver these notifications to your households ("End-users") e.g. via Firebase Cloud Messaging.
The MOOST Recommender Platform delivers Notifications to Customer’s specified REST Endpoint. The Endpoint that should be used can be configured as a per Customer, per End-user or a combination of both.
To send notifications to the REST Endpoint, the Endpoint has to be exposed on a public domain that can be accessed via Internet. Any REST Endpoint that is accessible via Internet should be protected via authentication. The MOOST Recommender Platform is able to authenticate against a Customer’s REST Endpoint via various authentication methods.
The Recommender Platform is able to authenticate against a Customer REST Endpoint via various authentication methods as listed below.
The Recommender Platform can be configured to authenticate against a customer’s REST endpoint with username and password (i.e. “Basic” authentication).
The Recommender Platform can be configured to use an API-Token to authenticate against a customer REST Endpoint.
The Recommender Platform can be configured to use a Bearer Token to authenticate against a Customer REST Endpoint.
If the Customer’s REST Endpoint is protected against DDOS attacks with some kind of request throttling the Customer should inform MOOST during the integration phase about the limitations that are in place. MOOST will configure the Recommender Platform accordingly.
If the limits are exceeded, the MOOST Recommender Platform will not able to send all notifications back to the Customer’s REST Endpoint. Cusermers are encouraged to ensure that the chosen limitation is in line with the expected notifications per time unit.
An example of a notification object which will be sent to the Customer’s REST Endpoint is shown below. The notification object will be posted to the specified Customer’s REST Endpoint as a JSON message in the body.
A notification includes two actions that should be presented to the End-user. The actions consists out of a text field which contains the text that should be presented to the End-user in the different languages, and a action qualifier field, which describes the type of action (and which should be returned to the MOOST API when the action is selected by the end-user).
The Recommender Platform has the following action qualifiers:
DISMISS
OPENAPP
STOPDELIVERY
OPENWEB
The DISMISS
actionQualifier states that the push notification should be dismissed when this action is selected be the end-user.
The OPENAPP
action states that when this action is selected by the the end-user, then the app should be opened. The optional parameter attribute may contain a language specific value, such as e.g. an URL or a use case name.
The STOPDELIVERY
action states that when this action is selected the push-notification should be dismissed and the actionQualifier should be returned to the MOOST API implicating that no more notifications of this type should be sent to the End-user.
The OPENWEB
action states that when this action is selected by the the end-user, then a browser should be opened. The optional parameter attribute may contain a language specific value, typically an URL.
Optionally, you may specify a command when defining a notification in a rule. The command
field may contain an instruction for a machine-to-machine interface so that some changes could be triggered.
As this is customer specific, this field is initially empty, but can be defined by the customer to his preferred format.