Remove reaction
Allows users to remove their previously-posted message reactions, by specifying the parent message, and the single timetoken of the reaction(s) they wish to delete.
It is technically possible to delete more than one reaction if the same UUID/userId posted different reactions 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.
Path Parameters |
---|
sub_key string — REQUIREDYour app's subscribe key from Admin Portal. Example:
|
channel string — REQUIREDThe channel name to perform the operation on. Example:
|
message_timetoken string — REQUIREDThe publish timetoken of a parent message. Example:
|
action_timetoken string — REQUIREDThe publish timetoken of the reaction. Example:
|
Query Parameters |
---|
auth stringString 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:
|
uuid string — REQUIREDA UTF-8 encoded string of up to 92 characters used to identify the client. Example:
|
signature stringSignature 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. |
timestamp integerUnix epoch timestamp used as a nonce for signature computation. Must have no more than ± 60 seconds offset from NTP. Required if the |
Responses | |||||
---|---|---|---|---|---|
200 The reaction was removed.
| |||||
207 The reaction was deleted but the action-deletion message was not published.
| |||||
400 Wrong uuid specified for the given message reaction.
| |||||
403 The client isn't authorized to perform this operation.
|