Notification objects are created either automatically as a result of connection invitations or manually in the Custom Notifications section of the administrator portal.
Through the administration interface at https://app.dev.medable.com/[your_org_name]/settings/notifications, notifications can be enabled, disabled, or based on organization members’ preferences.
In conjunction with the scripting application programming interface (API), custom notifications can be configured for multiple endpoints and sent via scripts, for example, require("notifications").send("c_my_notif");.
An organization can set up an app for Apple Push Notification Service(APNs) and Google's Firebase Cloud Messaging (FCM), and users can set preferences for how to receive notifications: through APNs, via email, or through SMS for custom notifications.
Note: For customers who cannot use APNs or FCM, Medable incorporates the Tencent notification system.
For more information contact your Medable representative for more information.
Notifications are automatically cleared for connection invitations when they are retrieved using the API. Otherwise, clients should manually clear them using the notifications API.
The notification identifier.
The context for which the notification was created.
The date the notification was created. Notifications that are not acknowledged expire after 30 days.
An object containing notification metadata. For post updates, for example, it contains the postId and postType. For comments, it also contains the commentId.
The object name (notification).
The notification type. See Consts for the standard notification type _ids.