Notification Object

Notification objects are either automatically created as a result of connection invitations or manually created via the Custom Notifications section on the admin portal.

Through the administration interface at https://app.dev.medable.com/{your_org_name}/settings/notifications, notifications can be enabled, disabled, or based on org members’ preferences.

In conjuction with the scripting api, custom notifications can be configured for multiple endpoints and sent via script (e.g. require("notifications").send("c_my_notif"); ).

An Organization can setup an app for Apple Push Notification Service (APNs) and Google Cloud Messaging (GCM), and users can set preferences for how to receive notifications, through APNs, via email or through SMS for custom notifications.

Notifications are automatically cleared for connection invitations when they are retrieved using the API. Otherwise, clients should manually clear them using the notifications API.

_id ObjectId	The notification identifier.
context Reference	The context for which the notification was created.
created Date	The date the notification was created. Notifications that are not acknowledged expire after 30 days.
meta Any	An object containing notification metadata. For post updates, for example, it contains the postId and postType. For comments, it also contains the commentId.
object String	The object name (notification).
type ObjectId	The notification type (See Consts for the standard notification type _ids)

Example Notification Object

{
  "_id": "55238637b9b285167a241439",
  "context": {
    "_id": "5519c01aae2fd2b02915c81f",
    "object": "c_example",
    "path": "/c_examples/5519c01aae2fd2b02915c81f"
  },
  "meta": {
    "postId": "55238637a033479c18311c6e",
    "type": "c_post"
  },
  "object": "notification",
  "type": "4e66204665656473506f7374"
}