Allows users to remove their previously-posted message actions, by specifying the parent message, and the single timetoken of the action(s) they wish to delete.
It is technically possible to delete more than one action if the same UUID/userId posted different actions on the same parent message at the same time. If all goes well, the action(s) are deleted from the database, and one or more
Action remove event messages are published on the same channel as the parent message.
Your app's subscribe key from Admin Portal.
The channel name to perform the operation on.
The publish timetoken of a parent message.
The publish timetoken of the action.
String which is either the auth key (PAM v2) or a valid token (Access Manager) used to authorize the operation if access control is enabled.
Example: myAuth / p0thisAkFl043rhDdHRsCkNyZXisRGNoYW6hanNlY3JldAFDZ3Jwsample3KgQ3NwY6BDcGF0pERjaGFuoENnctokenVzcqBDc3BjoERtZXRhoENzaWdYIGOAeTyWGJI
A UTF-8 encoded string of up to 64 characters used to identify the client.
Signature used to verify that the request was signed with the secret key associated with the subscribe key.
If Access Manager is enabled, either a valid authorization token or a signature are required.
Check Access Manager documentation for details on how to compute the signature.
Unix epoch timestamp used as a nonce for signature computation. Must have no more than ± 60 seconds offset from NTP.
Required if the
The action was removed.
The action was deleted but the action-deletion message was not published.
Wrong uuid specified for the given message action.
The client isn't authorized to perform this operation.