| Name | Type | Description | Notes |
|---|---|---|---|
| channel | Option<Channel> | The way the notification will be delivered to the user. All notifications created through the API will be of notification type API_NOTIFICATION, channel PUSH, and will not be associated to an entity. No other channels are supported. (enum: EMAIL, SMS, PUSH, IN_APP) |
[optional] |
| content | Option<String> | The main body of the notification text sent to the user. | [optional] |
| created_at | Option<String> | The date and time the notification was created, represented in ISO 8601 format with a timestamp. | [optional] |
| deep_link_guid | Option<serde_json::Value> | The unique identifier for objects that directly trigger a notification. For example, TRANSACTION_FEE_CHARGE and TRANSACTION_EXPENSE_LARGE notification types will have a transaction guid in this field. |
[optional] |
| delivered_at | Option<serde_json::Value> | Date and time the notification was delivered, represented in ISO 8601 format with timestamp. | [optional] |
| entity_guid | Option<serde_json::Value> | The unique identifier of the entity that the notification is attached to. | [optional] |
| guid | Option<serde_json::Value> | Unique identifier for the notification. Defined by MX. | [optional] |
| has_been_delivered | Option<serde_json::Value> | Indicates if the notification has been delivered to the user. | [optional] |
| has_been_viewed | Option<serde_json::Value> | Indicates if the notification has been viewed by the user. | [optional] |
| notification_type | Option<serde_json::Value> | The type of notification. See Notification Types. | [optional] |
| subject | Option<serde_json::Value> | The notification summary text. Usually the same text used for “in-app” or SMS notifications. | [optional] |
| threshold | Option<serde_json::Value> | [optional] |