Delete Notification

delete

/mobile/system/notifications/notifications/{id}

Deletes a notification. You can delete a notification only if its status is Scheduled.

If you are using BASIC authorization, and the notification is for a different mobile backend, then the Oracle-Mobile-Backend-ID header must identify that mobile backend, and not the backend that your app is associated with.

Permissions

To access this operation, you must be a team member with the MobileEnvironment_Notifications role.

Request

Path Parameters
Back to Top

Response

Supported Media Types

204 Response

The notification was deleted or doesn't exist. No content is returned.

400 Response

The notification ID is missing or can't delete the notification.
Body ()
Root Schema : Error
Type: object
Title: Error
The error JSON object returned by Mobile Cloud Service.
Show Source
Nested Schema : o:errorDetails
Type: array
Minimum Number of Items: 0
List of the issues that cause the error. Included when the error is caused by multiple issues.
Show Source
Nested Schema : Error Detail
Type: object
Title: Error Detail
Show Source
Back to Top

Examples

This example shows how to use cURL to cancel a scheduled notification by submitting a DELETE request on the REST resource.

curl -i \
-X DELETE \ 
-u team.user@example.com:password \
-H "Oracle-Mobile-Backend-ID: ABCD9278-091f-41aa-9cb2-184bd0586fce" \
http://fif.cloud.oracle.com/mobile/system/notifications/notifications/3

Example of Response Header

Here's an example of the response header. The HTML status 204 indicates that the notification was either deleted or it didn't exist:

204 NO_CONTENT
Date: Tue, 23 Jun 2015 00:21:33 GMT
Back to Top