Skip to content

Cancel Scheduled Message

Delayed delivery as well as repeated publish messages can be canceled using the API documented below:



Endpoint URL

The is a subdomain assigned to your application. For more information see the Client-side Setup section of this documentation.<message-id>


Argument                Description
<message-id> ID of the message to cancel.

Request headers

Content-Type: application/json  
user-token: optional value obtained as a result of the login operation.


Argument                Description
Content-Type Must be set to application/json. This header is mandatory.
user-token Optional header. Contains a value returned by Backendless in a preceding user Login API call. If user-token is set in the request, the operation will be executed with the security policy associated with the currently logged in user. This means all the permissions and roles assigned to the user will be enforced by Backendless.

Request Body


Response Body

  "status" : "failed" | "canceled",  
  "messageId": messageId  


When the server-side reports an error, it returns a JSON object in the following format:


The following errors may occur during the message cancellation API call:

Error Code
Message has already been canceled or does not exist.



Make sure to replace xxxx in the domain name in the sample request below to the one assigned to your application.

curl -X DELETE \