GET | /api/notifications/definitions | List all notification definitions |
---|
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
ResponseStatus | form | ResponseStatus | No | |
Notifications | form | List<Notification> | No |
Name | Parameter | Data Type | Required | Description |
---|---|---|---|---|
NotificationGuid | body | Guid | No | |
Enabled | body | Boolean | No | |
Name | body | String | No | |
Description | body | String | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json
To embed the response in a jsonp callback, append ?callback=myCallback
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
GET /api/notifications/definitions HTTP/1.1 Host: api.secure-messaging.com Accept: application/json
HTTP/1.1 200 OK Content-Type: application/json Content-Length: length { "responseStatus": { "errorCode": "String", "message": "String", "stackTrace": "String", "errors": [ { "errorCode": "String", "fieldName": "String", "message": "String", "meta": { "String": "String" } } ], "meta": { "String": "String" } }, "notifications": [ { "notificationGuid": "00000000000000000000000000000000", "enabled": false, "name": "String", "description": "String" } ] }