In some examples, if authentication data is required to authenticate the user and/or the user computing device requesting the subscription, the subscription management component 116 can determine authentication data (e.g., based on authentication data input via the subscription user interface 400, accessing authentication data stored in the datastore 122, etc.) and can send the authentication data to the third-party server(s) 154 (e.g., with consent of the user). The third-party server(s) 154 can return an authentication indicator (e.g., a token), which can be stored by the server(s) 102 to indicate that the user is authenticated to receive notifications via the subscription.
In at least one example, based at least in part on the subscription being generated, an indication of the subscription can be presented via the user interface 200, for example, proximate to other indication(s) of other existing subscription(s). As illustrated in