Input
In this example, we're filtering notifications by their source using the triggers string. Other filters include:
Show Read: Set to true to include previously read notifications.
Priority: Fetch notifications of a specific priority.
Of Type: Fetch notifications of a specific type, such as PullRewardAcquired for triggers and purchased items. If there are many notifications, use pagination to navigate through the data.
Mark as read
Once a notification is processed in your game logic, mark it as read. This will exclude it from future requests unless you specifically request read notifications. This action should be applied to each item in the list of handled notifications.
Logic for handling Notifications
When listing notifications, branch the completed event based on the success flag and add error handling for failed requests.
Note on Pagination: The notification response includes pagination data to help you navigate large notification lists.
We recommend branching the completed event from listing notifications on the success flag, and if you do this you will probably want to add error handling in case the request fails.
Here, we retrieve only unread notifications from the triggers source with default pagination (up to 10 items). We then filter further by SuccessfullyInvokedTriggerKey to narrow the list to specific triggers.
In this example, we simply print the notification info. Adapt this step to handle notifications based on your game’s requirements. Here, we assume that SuccessfullyInvokedTriggerKey provides a currency reward and only expand that information.
For a more general approach, iterate over all notifications to handle various sources and rewards relevant to your game.
