NotificationController Methods

POST /Notification/ Creates a notification.

DELETE /Notification/{id} Deletes an notification.

If the current context is not already the specified context, creates a new caller context which is a clone of the specified context and sets it as the current one.

Ensures when form files are access the content is MIME multi-part which we want.

GET /Notification/Account/{id} Gets the notifications for the specified account.

Gets the client ID from cookie or from the provided value, which is usually from the query string.

GET /Notification/CurrentUser/ Gets all notifications for the current user.

GET /Notification/{id} Gets the notification that has the specified ID.

GET /Notification/ OBSOLETE - Use GET /Notification/CurrentUser instead. Gets all notifications of the current user.

POST /Notification/GetNotificationsForAccount/{id} OBSOLETE - Use GET /Notification/Account instead. Gets the notifications for the specified account ID.

Gets the requested service.

Gets the session ID from cookie, the authorization header or from the provided value, which is usually from the query string.

Creates a new caller context associated with the specified session ID. The session is not validated.

POST /Notification/Query Gets multiple notifications.

POST /Notification/Count/ Gets the number of accounts that match the filter.

Retrieves the first form file from the request.

Retrieves the form files from the request.

Returns the invalid windows identity response to challenge the browser.

POST /Notification/Run Runs multiple notifications.

PUT /Notification/ OBSOLETE - Use POST /Notification/ or PUT /Notification/{id} instead. Save a notification.

PUT /Notification/Toggle Toggles the status of multiple notifications.

PUT /Notification/{id} Updates a notification.